Allow custom build/link configuration, decouple core CLI infrastructure from code assets, data assets, ...

pkgs/native_assets_builder/CHANGELOG.md

@@ -21,6 +21,11 @@
   consistency of the sum of those parts. Effectively this means: Any asset that
   doesn't have an explicit linker will get a NOP linker that emits as outputs
   it's inputs.
+- **Breaking change** Removes knowledge about code & data assets from
+  `package:native_assets_builder`. Users of this package can know hook into the
+  build/link hook configuration that is used and e.g. initialize code
+  configuration. Similarly users of this package now have to provide a callback
+  to verify the consistency of the used hook configuration.
 
 ## 0.8.3
 

pkgs/native_assets_builder/lib/src/build_runner/build_planner.dart

@@ -47,7 +47,7 @@ class NativeAssetsBuildPlanner {
     );
   }
 
-  (List<Package> packages, bool success) plan({
+  List<Package>? plan({
     String? runPackageName,
   }) {
     final PackageGraph packageGraph;
@@ -62,7 +62,6 @@ class NativeAssetsBuildPlanner {
     final packagesToBuild = packageMap.keys.toSet();
     final stronglyConnectedComponents = packageGraph.computeStrongComponents();
     final result = <Package>[];
-    var success = true;
     for (final stronglyConnectedComponent in stronglyConnectedComponents) {
       final stronglyConnectedComponentWithNativeAssets = [
         for (final packageName in stronglyConnectedComponent)
@@ -73,13 +72,13 @@ class NativeAssetsBuildPlanner {
           'Cyclic dependency for native asset builds in the following '
           'packages: $stronglyConnectedComponentWithNativeAssets.',
         );
-        success = false;
+        return null;
       } else if (stronglyConnectedComponentWithNativeAssets.length == 1) {
         result.add(
             packageMap[stronglyConnectedComponentWithNativeAssets.single]!);
       }
     }
-    return (result, success);
+    return result;
   }
 }