microsoft / microsoft/language-server-protocol

A client cannot inform the server that some dynamic registrations have failed

Open
#1,353 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I'm interacting with a server that is sending a client/registerCapability method with a number of registrations. One of them is being sent in error. The client specifically indicates that it does not support one of the capabilities being registered. However, there does not appear to be a way for the client to indicate that only some of the registrations succeeded.

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 with the client/registerCapability method and the case where a batch contains an unsupported registration. Determine how the protocol should represent partial success, then document the expected client and server behavior and verify that the specification consistently describes the result.

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.