microsoft / microsoft/language-server-protocol
Clarification: diagnostic ranges
Open
Nobody has claimed this yet.
clarification
diagnostics
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
VSCode supports a few diagnostic ranges that aren't documented in the LSP spec:
- If a diagnostic's range has start and end position the same, then VSCode will squiggle the word at that position.
- If a diagnostic's range has end position at character
Number.MAX_VALUE, then VSCode will squiggle to the end of the line.
I think the LSP spec should call out these two cases, so that other clients implementing it will be sure to do the same.
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 locating the diagnostic range section in the LSP specification and compare its wording with the two VSCode behaviors described here. Document the same-position and Number.MAX_VALUE end-position cases, with completion marked by both behaviors being explicitly covered in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100