Clarify --config option (provide example) about purescript-language-server HOT 3 CLOSED

Well, that does say pass config or send config on starting, so I presume either the vim stuff is now sending config or I changed something, we should figure that out.

Basically there is some config that is only read once at startup, and there is a mechanism in the LSP to send config, vscode always sent this at the start so we waited for that to be sent before proceeding, unless it was passed on the command line.

Would be good to reevaluate this.

Regarding the actual content, the possible values are basically here https://github.com/nwolverson/vscode-ide-purescript/blob/master/package.json#L77 but it would definitely be useful to have an example of what this looks like in JSON. The only config I could confidently give from memory is this one: {} 😄

from purescript-language-server.

Managed to get it working, turned out this flag is optional. So the following paragraph is a bit misleading (I'd replace should -> may):

Currently you should pass a --config flag followed by a JSON object, or immediately send config on starting the server in the same way VS Code does - this should improve in future

from purescript-language-server.

Thanks for your explanation! Please reopen this issue if needed

from purescript-language-server.