microsoft / microsoft/vscode-languageserver-node
Capture exit code of failing lsp server?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
Is there a way to hook the LanguageClient to report the exit code for a LSP server? Neither the initializationFailedHandler nor ErrorHandler options of the LanguageClientOptions seems to work for this.
https://github.com/microsoft/vscode-languageserver-node/tree/master/client
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 client implementation in the linked vscode-languageserver-node repository and trace how LanguageClientOptions, initializationFailedHandler, and ErrorHandler handle a failed LSP server. Determine whether the client exposes the server exit code and define a completion check for reporting it through a supported hook.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100