DesModder / DesModder/DesModder
Parse defined keys to Typescript, or vice versa.
Open
Nobody has claimed this yet.
dev-enhancement
localization
- Dominant language
- TypeScript
- Stars
- 134
- Forks
- 49
- Avg merge
- 5h 2m
- Merged PRs (30d)
- 15
Description
Some vague ideas. It would be nice to:
- check for missing keys. Surely this is implemented somewhere.
- check for keys in excess of those defined in en.ftl.
compare translations side-by-side (better than a diff). This might be a VS Code plugin.- parse defined keys to Typescript, or vice versa. Guards against typo'ing translation keys.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions translation keys defined in en.ftl and their use in TypeScript, but no repository files or entry points are identified. First locate en.ftl and the existing missing/excess-key checks, then determine whether the project should generate TypeScript definitions or validate keys against them. Done means typo-prone translation keys are checked in the chosen direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100