OmniSharp / OmniSharp/csharp-language-server-protocol
Support for pull-based diagnostics?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 638
- Forks
- 109
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
Pull-based diagnostics are being discussed at https://github.com/microsoft/language-server-protocol/issues/737 , and there's a proposal with an implementation at https://github.com/microsoft/vscode-languageserver-node/blob/main/protocol/src/common/proposed.diagnostic.md .
I noticed that this repo sometimes implement proposals before they are finalized; is that planned for this one?
Thanks!
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 reviewing the pull-based diagnostics discussion in microsoft/language-server-protocol issue 737 and the proposed diagnostic specification in vscode-languageserver-node's protocol/src/common/proposed.diagnostic.md. Determine whether this repository plans to support the proposal and what concrete scope would be required; done is an agreed implementation plan or a clearly defined follow-up issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100