Andrew Kolos

> This is not supported and violates many assumptions in the tool. @christopherfujino, we've discussed this recently, but—for the sake of public documentation—do you have any examples of such assumptions...

@reidbaker would it make sense for someone on the Android team to do the first review pass here? I don't have a great understanding of activity aliases or why/if we...

> @andrewkolos Is it possible that this test is not using the unified Java logic? > > We think that because this is pure Dart executing the Flutter tool that...

FYI this is what multiple `assets` section errors looks like from the user's perspective: ``` Error detected in pubspec.yaml: Unable to parse assets section. In flavors section of asset "assets/a.txt":...

Thanks for the great investigation work! This is indeed a nasty bug where running `flutter test`, updating an asset file's contents, and then running `flutter test` will result in tests...

> > Users author Dart packages that transform a file. These packages follow two rules: 1) they accept (the location of) an input file via an `--input` option, and 2)...

> For the native assets feature, dartdev and flutter_tools do the invocation with a dart /absolute/path/to/hook/build.dart, instead of relying on dart pub run.? How are the dependencies of the package...

Closing as completed since documentation has landed.

Rerouting to the tools team since this is _probably_ a tool bug (the PR introducing the `--dart-define-from-file` feature was reviewed by the tools team). For whatever it's worth, the framework...

Hello, sorry for the prolonged silence. This is back on my radar, and I will do my best to provide another review within the next couple of days.