-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Name collision with flutter localization when using build_runner. #49
Comments
A temp workaround is to comment
|
I'm sorry for the late reply. Just now we released
flutter_gen:
null_safety: true # Optional (default: true)
dev_dependencies:
build_runner:
flutter_gen_runner: ^3.0.2 # Since v2, renamed |
I can confirm that it now works and has no conlficts with flutter's new l10n package using build_runner(tested under flutter 2.0.0). Thanks a lot for this awesome package @wasabeef |
I confirm it does work without conflict with |
@wasabeef san, It worked. If we don't have the config
=> After run build runner -> it doesn't work.
If I remove those config (flutter_gen) in pubspec.yaml => I can build & run app normaly. It looks like the key I tested with |
@wasabeef san, Detail:
=> After the build_runner run completed (without out error). => Build & run app => the error display with message WORKAROUND |
It seems that still doesn't work with custom config in pubspec.yaml. Any updates on this? |
Which
|
Does anyone have new take on this? It is still present in 5.1.0+1 |
Seems like a flutter issue. |
There is nothing the package can do until the virtual |
And should also be solved by #53 (comment). |
This package has the exact same name than the official flutter localization package, resulting in name collision.
After importing flutter_gen package (this package), my localization files are broken.
error: Target of URI doesn't exist: 'package:flutter_gen/gen_l10n/app_localizations.dart'.
Any ideas ?
EDIT
I just found that the file ".dart_tool\package_config.json" contains a ref to flutter_gen-1.2.1
And this package is currently at 1.2.1, so I guess the plugin used by Flutter is this one ? So it's the same package after all ?
But why it collides then ?
The text was updated successfully, but these errors were encountered: