-
Notifications
You must be signed in to change notification settings - Fork 15
Problem decoding completion responses #69
Comments
This looks like an decoding issue with haskell-lsp, trying to decode that bit of JSON there gives:
|
Thanks for reporting this. Can you try out haskell-lsp master now and see if this fixes your crash? If that works then we can make a new release |
I didn't want to look into how to build a Haskell library manually right now, but I can confirm that forcing every completion item to have a |
If you're using a cabal.project, try dropping this in
|
Any chance for a bugfix release including the fix? I can work around it by pulling from git, but it would be nicer if I could just point at a hackage release, thanks for the great library! |
@kritzcreek haskell-lsp-0.23.0.0 and haskell-lsp-types-0.23.0.0 are up on hackage now, and lsp-test should have a new revision bump for them too! |
Wow, what was quick! Thank you :) |
Since updating from lsp-test 0.10 to 0.11, I get the following error in my tests:
Tests for other LSP methods still work, so it must really be something specific to how responses to completion requests are decoded. I also tried to make my server return a
CompletionList
object instead of just a list ofCompletionItem
objects, but that didn't help either.The text was updated successfully, but these errors were encountered: