microsoft / microsoft/vscode-languageserver-node
Allow clients of the LSP library to capture all errors and show customized / localized message.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
Hi) I've faced with some not localized phrases in products use your module.
Some packages throw errors and exceptions without any processing (for example: package vscode-languageserver).
Could you, please, add localization for theese phrases?
For example, I faced with that and some other messages:
Thanks in advance)
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
Start with the referenced jsonrpc/src/common/connection.ts entry point at line 1522 and inspect how vscode-languageserver and other packages propagate errors and exceptions. Clarify the scope and API needed for clients to capture, customize, and localize all such messages before defining completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- devtools, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100