Skip to content

I18nFileLoadError for locales ‘am’ and ‘ml’ due to Misidentification in load_directory #43

Description

@achivkin

Body

Hello,

When the user's locale is set to 'am' or 'ml', the code in the load_directory function of resource_loader.py incorrectly assumes that a corresponding localization file exists. This leads to an i18n.loaders.loader.I18nFileLoadError. The error message displayed is:

I18nFileLoadError: error getting data from resources/translations/de.yaml: ml not defined

This issue arises due to improper file existence checking. The locales 'ml' and 'am' are mistakenly identified as existing because they are substrings of the ".yaml" file extension. This results in the erroneous assumption that the relevant localization files are present.

Suggested Fix

A more robust method of checking for the existence of localization files should be implemented to prevent substring matches within file extensions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions