Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The test passes, and I cannot repro the issue with VSCode, so the issue must be down to a difference in how CoC and VSCode implement the LSP spec.
I believe it worked before the lsp-1.0 upgrade, which means that something has changed between haskell-lsp and lsp in how the initial configuration is handled.
The full LSP log (see the Gist below) from the test shows that lsp-test generates a
workspace/didChangeConfiguration
with the formatter config. It could be that CoC doesn't send this notification, and instead expects the server to request the config. @wz1000 @bubba is it possible that haskell-lsp does request the config at startup, whereas lsp does not?https://gist.github.com/pepeiborra/fcad435bdf8717ceeecf392549329c19
There's nothing else to do here, so this closes #1376. The next step is to either teach lsp to request the config at startup, or get CoC to send the
workspace/didChangeConfiguration
as VSCode does. /cc @andys8I also took the chance to remove an unnecessary use of the AGPL flag in the test suite