Closed adil192 closed 1 year ago
Thanks for noticing this UX issue!
I think that applying unchanged translations is never useful. So instead of adding a flag, flutter pub run slang apply
will only apply changed locales by default. The developer can still use --locale=
to apply a specific locale where it might be the same (en-US
, en-GB
).
Changed in v3.14.0
Motivation When I'm applying translations, there is usually only one language that's changed at a time. I therefore need to type in
which is quite tedious especially with the longer locale codes.
Developer Experience I propose a new flag, e.g.
which would only apply translations from locales that have changed from the default translation file.
e.g.
Running
flutter pub run slang apply --only-changed
on the above would be equivalent to