microsoft / microsoft/language-server-protocol

Automatic discovery of Language Servers

Open
#2,051 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request new request
Dominant language
TypeScript
Stars
13k
Forks
1k
Avg merge
6d 1h
Merged PRs (30d)
10

Description

Currently each IDE needs to be configured for each Language Server implementation. It would be nice if there was a way for IDEs to automatically detect installed servers.

This is possible for Jupyter kernels, each Jupyter kernel installs its config in ~/.jupyter and VSCode can automatically detect all installed Jupyter kernels, no need for any additional configuration or extensions.

Similar setup should work for LSP. There can be some standard folder like ~/.lsp. Each installed Language Server would store its config there. This config will specify command to run the server and will contain a list of supported file patters (e.g. file extensions and special files like package.json or Cargo.toml to look for). If IDE detects that there is a Language Server suitable for the current file/directory it could ask user to run it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Jupyter kernel discovery precedent described in the issue and the proposed ~/.lsp configuration model. No repository files, tests, or implementation entry points are named; the work is complete only after the discovery format, server configuration, and IDE matching behavior are specified and agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter, vscode
Domain
developer-experience, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.