Set resolveProvider capability to false #67
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.
It's my understanding that the
resolveProvider: trueproperty in thecompletionProvidercapability in the Language Server Protocol (LSP) signals that the language server can resolve extra details for a completion item. A language server that specifiesresolveProvider: trueshould typically implement acompletionItem/resolvehandler, which the client will call to resolve a completion item returned from thetextDocument/completionrequest.The client I'm using, helix, checks the
completionProvidercapbility, seestrue, and callscompletionItem/resolve. Since theemmet-lsconnection doesn't implementonCompletionResolve, this causes a "method unhandled" error.The comment in
server.tssuggests thatresolveProvidermay have been set totruewith the assumption that it simply enables completion. It should befalseunlessemmet-lschooses to implementcompletionItem/resolve.