[FEATURE]: Allow LSP options to override project config location

[jwhitaker-gridcog]

Feature Description

It looks like the LSP options already allow specifying a global config location.
Any chance of allowing a local config override as well?

Use Case

Rationale i is basically I am trying to avoid config files littering up my repo root, so I'd like to put codebook stuff somewhere else.

Context is also I'm playing with using Codebook but no-one else on my team is and I don't have current plans to try and standardize.. I don't think that is relevant here, but including in case it is.

Proposed Solution

Adding configLocation to lsp initializationOptions

Alternative Solutions

No response

Examples

No response

Additional Context

No response

[blopker]

Hey! Thanks for the suggestion. Do you have an example of where you'd want to put it? I could also suggest putting the config into gitignore. There tends to be a bunch of editor-specific stuff in there already for most projects.

[jwhitaker-gridcog]

we would use toolConfig/codebook.toml, we have picked toolConfig for want of a wider standard c.f. nodejs/tooling#79
.