chore(i18n): translation contribution guardrails - #119
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sets up community translations now that the UI is translatable (#118), with
guardrails so a broken catalog can't merge.
What's here
web/scripts/check-i18n.mjsvalidates every catalog against the English sourceof truth: valid JSON, no key that English doesn't have, value shapes that match
(string vs plural map), and a manifest that only lists locales with a catalog.
Incomplete translations pass — missing keys fall back to English — and the
script prints per-language coverage. Runnable as
npm run check-i18n.merge rather than silently showing English.
claim a language.
Testing
locale (unknown key, wrong value shape, missing manifest entry).