I've recently stumbled upon a peculiar behavior of Flask-Babel that I believe being an error (unless of course I am missing something).
As the title says, the list_translations method does not return a config aware default translation (that is, when no translations are available). Instead, the default case (handled at lines 158-159) returns a Locale instance based on _default_locale.
Considering that default values for the configuration are set to the values of private properties (in init_app, including BABEL_DEFAULT_LOCALE that derives its default value from _default_locale) shouldn't list_translations return config aware value instead?
Greetings,
I've recently stumbled upon a peculiar behavior of Flask-Babel that I believe being an error (unless of course I am missing something).
As the title says, the list_translations method does not return a config aware default translation (that is, when no translations are available). Instead, the default case (handled at lines 158-159) returns a Locale instance based on
_default_locale.That contrasts with the way the topic is handled in default_locale, default_timezone and domain properties that all return config aware values.
Considering that default values for the configuration are set to the values of private properties (in init_app, including
BABEL_DEFAULT_LOCALEthat derives its default value from_default_locale) shouldn't list_translations return config aware value instead?