microsoft / microsoft/vscode-languageserver-node
Provide a LSP object validation layer
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
I noticed several traces of Notification handler 'textDocument/publishDiagnostics' failed with message: message must be set in debug console log. Unfortunately, i'm unable to find which language server is publishing diagnostic without message. it would be nice to provide more information. For instance: the uri, the error code, the Language server id if available, the range
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 by tracing handling of the textDocument/publishDiagnostics notification in the TypeScript LSP implementation and examine how invalid diagnostic messages are reported. Done means validation failures identify the URI, error code, language server ID when available, and range, making the publishing server easier to diagnose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100