Expose language-server connection or config

[agoose77]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

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.

[remcohaszing]

Please elaborate. Why do you need this? What’s the use case?

[agoose77]

I wanted to change the dictionary for retext-spell via a custom plugin. This is most naturally done by defining config schema, and sending the locale to the plugin over configuration. Presently, there's no mechanism for this.

[remcohaszing]

I strongly recommend to use a configuration file over VSCode settings. This is already supported. This means your CLI and language server can share the same configuration. Does this not work for you somehow?