Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error message for i18next key format rule #3543

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Improve error message for i18next key format rule #3543

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0a76d2e
Improve error message for i18next key format rule
Dec 21, 2024
621eecb
Merge branch 'develop' into improve-error-message
0xDC0DE Feb 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion typescript/react/portability/i18next/i18next-key-format.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,11 @@ rules:
- metavariable-regex:
metavariable: $DYNAMIC_KEY
regex: (?!^[`][a-z0-9-]+[.][a-z0-9-]+[.]\S+$)
message: Translation key '$KEY' should match format 'MODULE.FEATURE.*'
message: >
Translation key '$KEY' is invalid. Keys should follow the format 'module.feature.subkey':
- The 'module' and 'feature' parts must use only lowercase letters (a-z) and hyphens (-).
- Only the 'subkey' part may include uppercase letters, underscores (_), or periods (.).
- Example of valid format: 'my-module.my-feature.my_key'.
languages:
- typescript
- javascript
Expand Down
Loading