New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make polymer's build.dart smarter about entrypoints #20396
Comments
I'd rather get rid of build.dart altogether. Transformers should have a better contract with the analyzer. |
Agree - that's my long term goal too. This bug is to get one step closer and make build.dart as small as it can be, and get rid of the redundancy we have with the pubspec file until we reach that point. |
Set owner to @jakemac53. |
This comment was originally written by @zoechi Why is build dart needed anyway. Shouldn't this all be done by the analyzer? |
The analyzer is not aware of most of the polymer logic, so we use build.dart to show nice error messages in the DartEditor that we discover in our linter. One day we hope the analyzer will allow to have plugins so we can include polymer-specific logic that way. |
Fixed in r40286 Added Fixed label. |
This issue has been moved to dart-archive/polymer-dart#458. |
Now that the information is also in the pubspec.yaml, let's read it from there and not specify it twice.
This should make it very easy to write a build.dart as a single line Dart script:
export 'package:polymer/builder.dart'
The text was updated successfully, but these errors were encountered: