microsoft / microsoft/language-server-protocol
Code action support in LSIF
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
As mentioned in #825, I see a lot of potential in LSIF for tracking code smells in codebases and am working on an ESLint LSIF exporter. I'd also like to include in the LSIF dump how certain problems can be fixed automatically. LSP uses WorkspaceEdit for these, which can be serialized, and for complicated cases a Command reference can be included as a hint that the language server needs to be fired up to fix the problem. The code action can link to diagnostic vertexes.
Anything that speaks against adding this?
Spec link: https://microsoft.github.io/language-server-protocol/specification#textDocument_codeAction
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 reading issue #825 and the linked LSP textDocument/codeAction specification. Clarify how WorkspaceEdit, Command references, and links to diagnostic vertices should be represented in an LSIF dump, then define the protocol changes and validation needed for the feature to be considered complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100