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: true
property in thecompletionProvider
capability in the Language Server Protocol (LSP) signals that the language server can resolve extra details for a completion item. A language server that specifiesresolveProvider: true
should typically implement acompletionItem/resolve
handler, which the client will call to resolve a completion item returned from thetextDocument/completion
request.The client I'm using, helix, checks the
completionProvider
capbility, seestrue
, and callscompletionItem/resolve
. Since theemmet-ls
connection doesn't implementonCompletionResolve
, this causes a "method unhandled" error.The comment in
server.ts
suggests thatresolveProvider
may have been set totrue
with the assumption that it simply enables completion. It should befalse
unlessemmet-ls
chooses to implementcompletionItem/resolve
.