i18n-check CLI for dev teams to validate their localization files

[andrewtavis]

Hi all 👋 GitHub organizations I'm in are big Weblate users, so firstly thanks to the team and to the community! Really is so nice working with you all 😊

One of the communities I'm in that has extensive localization needs decided to work on a Python CLI to help the development team stay in sync with the work that's being done on Weblate. The result is i18n-check, which I'd like to introduce a bit and ask for feedback on :)

You set up the CLI with a YAML configuration file. The basic arguments it needs are the path to the project files (ex frontend), the directory where your Weblate files live (ex frontend/i18n), the Weblate source file (ex frontend/i18n/en.json) and the files types that you'd like to validate against (ex [.ts, .js]).

From there the CLI checks if:

• the code uses keys that aren't defined in the i18n source file
• the i18n source file has keys that aren't used in the code
• the locale files have keys that aren't in the source file
• there are repeat values in the source file
• your i18n files are sorted (for those sorting files in Weblate PRs and not wanting to deal with merge conflicts)
• there are missing keys in the locale files
• punctuation is correct for keys that you mark as being aria labels or image alt texts (keys ending in _aria_label/_alt_text)
• the keys are named appropriately such that the root is the file(s) in which it's used

We're using i18n-check in PR and pre-commit validation right now, and it's really helping to keep localization organized within a growing code base. As of now it just works with JSON i18n files, but if there's interest and capacity to support we'd welcome expanding it to other file types :)

Thoughts on the project would be very welcome! 😊