microsoft / microsoft/language-server-protocol

Add a S->C request/notification to update the clients config

Open
#1,692 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Example

{
  // scope
  "myLsp": {
    "ignoredIdentifiers": [
       // existing content...
       "file"
     ]
  }
}

This would update the clients myLsp.ignoredIdentifiers configuration.

Use Case

Take the following example:

file = { statement* }
statement = { "hello" | "goodbye" ~ ";" }

Our LSP for Pest would report file as an unused rule, as it is only used from Rust code (which our server has no knowledge of). This is why we have the alwaysUsedRuleNames config, which suppresses that warning.

We want to provide a quick fix to add file to that list, but as far as I can tell there is no way for the server to request an update to the client's configuration file.

Is this against the principles of the LSP or just something that hasn't been implemented?

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

The issue names no files or tests. Start by reviewing the language server protocol's existing server-to-client requests and configuration-related capabilities, then determine whether a client-configuration update request or notification fits the protocol. Done means resolving whether the behavior is permitted and, if so, specifying the protocol change and its client/server semantics.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design
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.