Ignore workspace/didChangeConfiguration #564
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Seems reasonable. I'm 99% sure my VS Code extension is coded to restart the server when the configuration changes, so it doesn't immediately make sense for the LSP to do anything more fancy for its sake, either |
|
Landed in 1.28.5 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
standardwith nvim-lspconfig, the server receives aworkspace/didChangeConfigurationmessage immediately after starting.Standard currently returns an
INVALID_SERVER_MESSAGEwhich causes neovim to display lots of angry errors.I've added a route to ignore this LSP message while logging that we're doing that.