Closed MatejKastak closed 2 years ago
the current implementation is not portable and doing some redundant work
VsCode extension is subscribed to the configuration changes
and sends the change using the custom LSP command
we can eliminate all of this by getting the configuration every time we set the context
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration
this approach also removes the need for the custom command and processing the events on configuration changes (for this entry)
the current implementation is not portable and doing some redundant work
VsCode extension is subscribed to the configuration changes
and sends the change using the custom LSP command
we can eliminate all of this by getting the configuration every time we set the context
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration
this approach also removes the need for the custom command and processing the events on configuration changes (for this entry)