Turns out that all the VS Code configurations can be read by the language server via the workspace/configuration server->client request.
When supported by the client, the client will respond with the values of all the configurations that were fetched.
Considering #471 now makes theme-check run on file open + change. I can see from a mile away that some of our users won't be happy about that 🙃 But it's the only way to have the diagnostics correctly "sync'ed" with the buffers. So we're going to turn that on by default. Still, we should give users the chance to opt out of that if they can deal with the linter running only on file save (and have the fix diagnostics only work after a file save).
Also, it turns out that all those configurations can also be set in CoC.nvim's config.json. Nice!
Turns out that all the VS Code configurations can be read by the language server via the workspace/configuration server->client request.
When supported by the client, the client will respond with the values of all the configurations that were fetched.
Considering #471 now makes theme-check run on file open + change. I can see from a mile away that some of our users won't be happy about that 🙃 But it's the only way to have the diagnostics correctly "sync'ed" with the buffers. So we're going to turn that on by default. Still, we should give users the chance to opt out of that if they can deal with the linter running only on file save (and have the fix diagnostics only work after a file save).
Also, it turns out that all those configurations can also be set in CoC.nvim's config.json. Nice!