Moritz
Moritz
Adding new assets in `link.dart` is not a priority I would say - but it would need some checking to avoid duplicating assets, or a policy on how to resolve...
We have the `ignore_packages` glob, which could be set to ignore anything beneath an `example/` folder by default, and then remove the special-casing of `publish_to: none`.
Yeah happy about any ideas for a nicer UX! We also probably want to link to more information about everything and add more docs while we are at it...
@polina-c is this still a P1 issue? It hasn't been updated in a while.
> Feedback and suggestions very much welcome/appreciated :) thanks! Just out of curiosity - why not go with protobuf?
@natebosch did you test this by flipping some repo using auto-publishing and PR health checks to `use-flutter: true`? That would be a good smoke test, before shipping this to all...
> using const DataAsset(package: 'foo', name: 'bar') is IMHO worse than const DataAsset('package:foo/bar'). I disagree. Using a "non-typed" API by requiring a string in a certain format is (IMO _much_)...
> We should have hook/build.dart use the same names as in lib/foo.dart > Strongly in favor of KISS design principle - keep things simple, not over-engineer APIs, ... Agree. >...
> Please test this in `flutter_tools` as well to see that the experience is consistent. You can make a checkout flutter and modify `flutter_tools` once you commit it rebuilds itself....
We shouldn't run it - or what do you mean?