-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Conflicts with source assets should have a better error message #14593
Comments
See also issue #14554. |
Marked this as blocking #14771. |
Issue #15668 has been merged into this issue. |
thanks for de-duping! |
Removed Area-Library label. |
Issue #16374 has been merged into this issue. |
Removed Library-Barback label. |
Issue #16748 has been merged into this issue. |
1 similar comment
Issue #16748 has been merged into this issue. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
I'm getting an "all emitted asset" error similar to the one described in this ticket when I run the Is there some way I can determine which asset is causing the conflict? |
Sorry for the emails, but I figured out the issue. If the build artifact already exists then |
This issue has been moved to dart-archive/barback#18. |
Right now when barback detects a conflict between a generated asset and a source asset, it displays it like so:
Transforms {Dart2JS on wordherd|web/solver/solver.dart} all emitted asset wordherd|web/solver/solver.dart.js.
This makes it look like a bug, since there's only one transformer there. The error should make it clear that the conflict was with a source asset on the physical filesystem.
The text was updated successfully, but these errors were encountered: