Skip to content

Clean unregistered featured from registration requests - #372

Merged
CGNonofr merged 1 commit into
mainfrom
fix-error-when-feature-not-registered
Jun 8, 2022
Merged

Clean unregistered featured from registration requests#372
CGNonofr merged 1 commit into
mainfrom
fix-error-when-feature-not-registered

Conversation

@CGNonofr

@CGNonofr CGNonofr commented Jun 3, 2022

Copy link
Copy Markdown
Collaborator

For some reasons, if the server sends a capability registration batch to the client and one feature is not registered on the client, all registration after it in the list won't be registered (see https://github.com/microsoft/vscode-languageserver-node/blob/a6f0d22d2c6842337ad135c13d2f945e53b1a6e4/client/src/common/client.ts#L1741)

Do you have a better idea?

@kaisalmen kaisalmen left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@CGNonofr I don't have better idea. How/when the exception is thrown must be done differently (e.g. result object / summary), then there is another way.

@CGNonofr

CGNonofr commented Jun 8, 2022

Copy link
Copy Markdown
Collaborator Author

The only other way is to create a PR on the vscode-languageserver-node itself, I'll try to have a look 👍

@CGNonofr
CGNonofr merged commit 5c31a8f into main Jun 8, 2022
@CGNonofr
CGNonofr deleted the fix-error-when-feature-not-registered branch June 8, 2022 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants