Initial checklist
Problem
I would like to access the configuration sent by the LSP client to the language server, but it is not exposed.
Current solutions
I'm currently writing the config to the file system, and checking (via stat) for changes to this file during runs. This is not ideal for performance.
Proposed solutions
Expose either the raw LSP connection object so that one can extend the LSP gracefully, or accept it as an argument that can be passed in.
Initial checklist
Problem
I would like to access the configuration sent by the LSP client to the language server, but it is not exposed.
Current solutions
I'm currently writing the config to the file system, and checking (via stat) for changes to this file during runs. This is not ideal for performance.
Proposed solutions
Expose either the raw LSP
connectionobject so that one can extend the LSP gracefully, or accept it as an argument that can be passed in.