microsoft / microsoft/vscode-cmake-tools
Migrate from `vscode-nls/vscode-nls-dev` to `vscode-l10n`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
The underlying libraries that facilitate string localization in VS Code extensions (vscode-nls/vscode-nls-dev) have been replaced with a new library: vscode-l10n.
https://github.com/microsoft/vscode-nls
https://github.com/microsoft/vscode-nls-dev
https://github.com/microsoft/vscode-l10n
Opening this issue to track migrating to the new library.
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 the linked vscode-nls, vscode-nls-dev, and vscode-l10n repositories, then inventory how the extension uses the existing localization libraries. Done means the project uses vscode-l10n in place of both older libraries and its extension localization remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- localization
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100