microsoft / microsoft/vscode-languageserver-node
Conform to the recommendation in the standard for the socket argument, which is currently `--socket` instead of `--port`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
Under Implementation Considerations in the LSP spec, the following arguments are laid out as highly recommended ways to standardize the CLI of starting a language server.
LSP:
stdio: (Unclear, but probably the default behavior without the pipe or socket arguments.)
pipe: The pipe / socket file name is passed as the next arg or with --pipe=.
socket: The port is passed as next arg or with --port=.
vscode-languageserver-node:
stdio: --stdio
pipe: --pipe=
socket: --socket=
This repository conforms for stdio and pipe, but not for socket.
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 CLI argument handling for socket mode and compare it with the LSP specification's Implementation Considerations, linked in the issue. The payload names no files, tests, or entry points; done means socket startup follows the specification's --port convention while preserving the stated stdio and pipe behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100