Description:

auto localized

auto_localized #
auto_localized is simplifying Flutter localization by using code generation.
This approach has many advantages such as runtime-safety and better performance. The generator checks translation files for
missing keys, blank values etc. and outputs easy to use dart fields (or methods).
Supported file types: JSON, YAML.

Generation time validation
Get translations without BuildContext
Safe Arguments
Supported file types: JSON, YAML


Getting Started #
Native setup #
On iOS you need to add supported locales to ios/Runner/Info.plist
Example:
<key>CFBundleLocalizations</key>
<array>
<string>pl</string>
<string>en</string>
<string>sk</string>
</array>
copied to clipboard
Pubspec setup #
Add dependencies to your pubspec.yaml:
dependencies:
auto_localized: <latest_version>

dev_dependencies:
build_runner: <latest_version>
auto_localized_generator: <latest_version>
copied to clipboard
Note: no need for adding flutter_localizations dependency: auto_localized does it for you.
If you store your translations files outside of lib folder (which you should), example structure:
lang/
├── en.yaml
├── pl.json
└── sk.json
lib/
build.yaml
pubspec.yaml
copied to clipboard
you need to tell build_runner about that, by overriding default sources
(by default you can reference a file only from lib directory). Create new (or update existing) build.yaml file on the root
of the project and add following section:
targets:
$default:
sources:
- $package$
- lib/**
- lang/** # <-- your translations directory
copied to clipboard
You can checkout sample configuration in the example.
Note: Adding translations directory to assets section in pubspec.yaml is not required. Flutter don't need these files at runtime.
Configuration #
Create new dart file with empty class and annotate it with AutoLocalized.
Example:
import 'package:auto_localized/annotations.dart';

@AutoLocalized(
locales: [
AutoLocalizedLocale(
languageCode: 'pl',
translationsFiles: ['lang/pl.json'],
),
AutoLocalizedLocale(
languageCode: 'en',
countryCode: 'US',
translationsFiles: ['lang/en.json'],
),
AutoLocalizedLocale(
languageCode: 'sk',
translationsFiles: ['lang/sk.json'],
),
],
)
class $Strings {}
copied to clipboard
Important: path to translation file must be relative. Class name have to start with $.
Name of that class will be used as name of translation container class - for the example above it will be: Strings.
Generation #
Run the generator with command in terminal:
flutter pub run build_runner build --delete-conflicting-outputs
copied to clipboard
Build can run automatically after every file change with:
flutter pub run build_runner watch --delete-conflicting-outputs
copied to clipboard
Usage #
In app declaration add generated config fields: supportedLocales and localizationsDelegates.
Also, if you want to get translations without context you need to wrap MaterialApp with AutoLocalizedApp:
return AutoLocalizedApp(
child: MaterialApp(
supportedLocales: context.supportedLocales,
localizationsDelegates: context.localizationsDelegates,
),
);
copied to clipboard
You can access these fields by AutoLocalizedData class or AutoLocalizedContextExtension.
Done! #
Translations are ready to use by:
Text(
Strings.welcome.get(context),
)
copied to clipboard
you can also get translations without context:
Text(
Strings.welcome.get(),
)
copied to clipboard
BuildContext extension is also here:
Text(
context.translate(Strings.welcome),
)
copied to clipboard
If you enable generateGetterMethods in annotation config you will get two additional ways:
//getter method
Text(
Strings.getWelcome();
)

//BuildContext extension
Text(
context.getWelcome();
)
copied to clipboard
Example #
For typical complete setup checkout example.
Features #
Safe Arguments #
You can define up to 5 arguments in for your translations, to define argument use syntax: {(number from 1 to 5)}
for example:
{
"welcome_message" : "Welcome {1}!, You have {2} points."
}
copied to clipboard
Result:
Strings.welcomeMessage('Marcin', '3');
copied to clipboard
Note: These arguments are required - The compiler will force you to pass these arguments.
You can also get args translation without applying them with getRaw() method.
Argument with given number can be used as much as you want, example:
{
"distance" : "Traveled: {2} {1} - Distance: {3} {1}"
}
copied to clipboard
You can get value for arg string with:
Strings.distance.get('km', '12', '30');
copied to clipboard
If you enable generateGetterMethods in annotation config you will get two additional ways:
//getter method
Strings.getDistance('km', '12', '30');

//BuildContext extension
context.getDistance('km', '12', '30');
copied to clipboard
There is also regular translate BuildContext extension method:
Text(
context.translate(Strings.welcomeMessage, 'Marcin', '3'),
)
copied to clipboard
This last method is unrecommended, because Dart does not support method overloading.
Compiler can't force you to pass all required arguments, default value for missing argument is "".
Annotation configuration #
auto_localized offers some configuration options for validation and code generation.



Option
Default value
Description




locales
-
List of AutoLocalizedLocale to associate language code (and optionally country code) with translations file. List can't be null or empty.


generateGetterMethods
false
When set to true apart from fields creates additional getter methods for generated fields and extension methods on BuildContext. This gives you the additional ways of getting strings.


convertToCamelCase
true
If set to true then any key case will be converted to camel case in generated source. For example key: { "test_message": "..." } will be generated to source: static const testMessage = LocalizedString(...); If set to false the original key will be used.


onBlankValueStrategy
error
Defines the behaviour when the value for key is blank or contains only whitespaces. Note: This behaviour is will not be triggered if value is explicitly defined as null. In that case generator will always throw an Error.


generateOfKeyFactories
false
When set to true you will gain access to additional methods ofKey and maybeOfKey. They will allow you to get LocalizedString at runtime with key from translation file. This feature is disabled by default because it introduces a point of possible runtime failure - use at your own risk.



Text getter #
Translation can be also accessed with text method that wraps string with Text widget
Strings.welcomeMessage.text(
arg: 'Marcin',
textAlign: TextAlign.center,
style: TextStyle(fontSize: 17),
);
copied to clipboard
Current locale #
You can access the current locale with:
AutoLocalization.instance.locale;
copied to clipboard
Locale update callback #
Often you would like to know when locale changes to perform different tasks: update network headers etc.
You can do that with AutoLocalization.addOnLocaleChangeCallback.
Example:
AutoLocalization.addOnLocaleChangeCallback((locale) {
//do stuff
});
copied to clipboard
To stop listening for updates use AutoLocalization.removeOnLocaleChangeCallback.
Example:

void onLocaleChange(Locale locale) {
//do stuff
}

AutoLocalization.addOnLocaleChangeCallback(onLocaleChange);

AutoLocalization.removeOnLocaleChangeCallback(onLocaleChange);
copied to clipboard
Additional #
Generate files have .al.dart extension, if You don't version controlling generated files don't forget to add it to .gitignore

License

For personal and professional use. You cannot resell or redistribute these repositories in their original state.

Share

• Share on Facebook
• Share on Twitter