microsoft / microsoft/language-server-protocol
Enable incrementally updating diagnostics
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
For large files I'm worried that sending information diagnostics will slow down editing, since the amount of information diagnostics scales with the size of the file, and there can be many edits that trigger sending new diagnostics.
Have you considered adding a reset/append enum to the PublishDiagnostics notification, or something more complicated, so it also becomes possible to append new diagnostics without resetting the existing ones?
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 PublishDiagnostics notification and its current replacement behavior. Review how diagnostics are resent after edits in large files, then define a protocol approach for reset and append semantics, including how clients know when the diagnostic set is complete. Done means a decided proposal with the necessary protocol specification changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100