microsoft / microsoft/vscode-languageserver-node
meta model should also include a programmatic description of the LSP state machine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
This is covering the various transitions expected from LSP when performing initial handshake and shutdown.
Something like this (https://github.com/microsoft/vscode/issues/4902#issuecomment-368583522) captured in the model.
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 the linked VS Code discussion and the issue description to understand the expected initial-handshake and shutdown transitions. Locate the existing meta model entry point, then define how the LSP state machine should be represented programmatically; the work is done when those transitions are captured in the model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100