Updates to generating localized messages #1796
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The use of synthetic package is deprecated and will be removed, see this breaking change description. Instead apps should generate the localized messages into source and PR fixes this.
These changes will not affect the way how we work with localizations. When we need to add a new string, let's just put it into
app_en.arb
and build the app to be able to use it in code.Changes:
app_localizations.dart
file.generated
folder is ignored in git and will be always created during build, but for making sure that nothing is broken, the pre-commit hook is updated so that it always regenerates the localized messages sources.AppLocalization.of(context)
now returns no-nullable getter.This has been tested on desktop and Android on both Flutter 3.27.4 and 3.29.0 versions.