You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I migrated from gen_l10n to slang, and the generated documentation is better in gen_l10n than in slang.
Since I am a native Japanese speaker, I need to be able to quickly preview member variables in Japanese, not just their names.
gen_l10n generates the following.
/// No description provided for @title. /// /// In en, this message translates to: /// **'Title'** /// /// In ja, this message translates to: /// **'タイトル'**Stringget title;
slang generates the following.
Stringget title =>'title';
The text was updated successfully, but these errors were encountered:
How about limiting this to only the base_locale? This functionality is useful to understand if the rendering is appropriate just by looking at the code.
I always jump to the declaration when I want to see the base translation (which is ctrl+left click). Don't know if the benefit is great enough to sacrifice the bigger file size
Motivation
I migrated from
gen_l10n
to slang, and the generated documentation is better ingen_l10n
than inslang
.Since I am a native Japanese speaker, I need to be able to quickly preview member variables in Japanese, not just their names.
gen_l10n
generates the following.slang
generates the following.The text was updated successfully, but these errors were encountered: