Do not set `Intl.defaultLocale` in generated output

[vainamov]

According to flutter/website#3013 it's no longer recommended to modify the Intl.defaultLocale field. This prevents issues that cause the language to change application-wide when using Localizations.override-widgets such as in flutter/flutter#40353.

Flutter Intl modifies the field in it's generated static Future<S> load(Locale locale) method. Afaik there is no way to customize this behaviour currently and obviously manually editing the generated file after each build is no long-term solution.

Please remove the aforementioned line from the output or add a new config option, so users can toggle the generation.

[lzoran]

Hi @vainamov,

Thanks for reporting this!

We are aware of this issue. As this is a breaking change for all existing users, we postponed this for the next major release of the intl_utils package (package that is used by the Flutter Intl extension for generating localization code).

Does usage of the Intl.withLocale work for you as an alternative until this is fixed?

...
import 'package:intl/intl.dart';
import 'generated/intl/messages_all.dart';

...

      // Somewhere in the widget
      FutureBuilder<bool>(
          future: initializeMessages('de'), // make sure you have loaded messages for the locale before usage
          builder: (BuildContext context, AsyncSnapshot<bool> snapshot) {
            if (snapshot.hasData) { // use messages once they are loaded
              return Text(
                Intl.withLocale('de', () => S.of(context).yourStringKey),
              );
            }

            return const Text('');
          }),
...

[vainamov]

Thanks for your reply @lzoran.

I'm afraid this won't help much. The issue I'm facing isn't that I cannot use Localizations.override() but rather that I can't not use it. See, the Flutter licenses dialog uses this widget and as such as soon as an user opens the dialog inside my app, the whole app is in English. The only two workaround options I'm currently seeing would be wrapping everything but the license dialog with your proposed solution (to force the app back to the selected locale) or to create an own version of the license dialog without the widget. I would rather prefer an option to configure the generation behaviour if I'm honest.

Do you have any timeline on when to expect an update to be ready to address this issue?

[aleksakrstic]

No defined timeline for this @vainamov