yoavbls / yoavbls/pretty-ts-errors
Tracking: Internationalization and localization
Open
Nobody has claimed this yet.
feature request
help wanted
- Dominant language
- TypeScript
- Stars
- 14.1k
- Forks
- 111
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
Description
This issue serves as a central hub for tracking all requests and discussions about support for internationalization and localization (I18n & L10n).
Goals
- Track progress on implementing internationalization and localization.
Reported issues
- https://github.com/yoavbls/pretty-ts-errors/issues/27
- https://github.com/yoavbls/pretty-ts-errors/issues/83
- https://github.com/yoavbls/pretty-ts-errors/issues/108
- https://github.com/yoavbls/pretty-ts-errors/issues/128
Related PR's
- https://github.com/yoavbls/pretty-ts-errors/pull/33
- https://github.com/yoavbls/pretty-ts-errors/pull/49
- https://github.com/yoavbls/pretty-ts-errors/pull/110
Notable Fork's
Resources
Contributor guide
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
Start by reviewing reported issues 27, 83, 108, and 128, then compare related PRs 33, 49, and 110. Read the VSCode localization API, vscode-l10n example, and TypeScript diagnostic localization resources. The issue does not define a specific entry point or completion criteria; done would require an agreed localization implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- internationalization, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100