-
Notifications
You must be signed in to change notification settings - Fork 7
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
Build.yaml no longer valid in latest build_runner #57
Comments
Hi talamaska! Can you show a minimal repo or part of your code for help? You should place both rosetta and rosetta_generator into dependencies. Maybe that was your problem. |
No, in the custom build.yaml where we point the folders to parse. We need to add an additional line in the end. |
You should change it in the example and in the docs. This change comes from build_runner with newer releases around flutter 1.20 release. |
Changes merged into stable |
Describe the bug
As noted in the docs I have added the following line in my build.yaml
In result I got some warnings and the generation is not working anymore
Also tried setting
rosetta_generator in place of just rosetta
When I remove the builders, the second warning disappears.
To Reproduce
Steps to reproduce the behavior:
flutter packages pub run build_runner build --delete-conflicting-outputs
Expected behavior
No warnings should be thrown
Desktop (please complete the following information):
[√] Flutter (Channel stable, 1.20.1, on Microsoft Windows [Version 10.0.18362.959], locale bg-BG)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Android Studio (version 4.0)
[√] VS Code, 64-bit edition (version 1.47.3)
[√] Connected device (1 available)
Flutter 1.20.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 2ae34518b8 (35 hours ago) • 2020-08-05 19:53:19 -0700
Engine • revision c8e3b94853
Tools • Dart 2.9.0
The text was updated successfully, but these errors were encountered: