Moritz
Moritz
Thanks for the quick feedback on this old issue! I will close it then.
Thanks for the tip! Was this recently/with a recent Flutter version? Unfortunately, I still can't reproduce the error. Reopening though.
@539863010, running `dart fix` should get rid of the unnecessary imports. That the "right" library has to be imported should be documented better.
This does show a need for more documentation around the `intl` package. I18n data is expected to change, so changes to that data are not breaking changes to this package....
I would like to keep the `intl_translation` package independent of Flutter implementation details, what are you trying to achieve exactly which can't be fixed with the current setup?
This is already now possible using glob syntax, see the readme. Or am I missing something?
The glob syntax is a bash feature, so for example using `dart run bin/extract_to_arb.dart $(find example/ -name '*.dart')` in the `intl_translation` root does do the trick. I agree however that...
Closing as there is no activity.
I usually roll out new locales with a CLDR update - so memo to myself to go through the list of missing locales with the i18n teams for the next...
Are these locales all needed by your project? As every locale adds to the size burden of this library, I would like to keep the number of supported locales at...