microsoft / microsoft/Power-Fx
Will diagnostic code be part of the LSP protocol diagnostics class?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.4k
- Forks
- 358
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 3
Description
In the official LSP specification, the "Code" parameter is defined as part of the diagnostics class, but it isn't defined in the class here. The "Code" parameter could be used for example to denote the inherent meaning behind the particular diagnostic, such as an error code.
Is this something that is planned to be added? I'll happily create a pull request if this is something that is valid.
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 src/libraries/Microsoft.PowerFx.LanguageServerProtocol/Protocol/Diagnostics.cs and compare its diagnostics model with the linked LSP 3.17 specification. Check how this protocol model is serialized and tested, if those locations are available. Done means the project’s decision is documented and, if accepted, the model matches the intended specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100