Open brainoutsource opened 5 years ago
Hello! I'm working on a tool which uses javascript-typescript-langserver among other LSPs.
javascript-typescript-langserver
Diagnostics work fine, but I'm having trouble (or am I?) with the way completion works. Consider the example:
1) I invoke completion (| is the position of the cursor I send with CompletionParams.Position):
|
CompletionParams.Position
document.body.|textContent = user;
and get all kinds of relevant stuff, starting with accessKey, and including the textContent.
accessKey
textContent
2) Now I invoke the completion here:
document.body.tex|tContent = user;
and I get the very same result, not filtered or sorted by the tex prefix.
tex
Is it an expected behaviour? Is it LSP client's job to sort/filter the completion suggestions? Thank you!
Btw, theia-ide/typescript-language-server/ displays the same behaviour.
I'm having the same issue. Any news on this?
Any update on this issue? this seems obviously even I use the vs plugin based on this lib, this issue still happen.
Hello! I'm working on a tool which uses
javascript-typescript-langserver
among other LSPs.Diagnostics work fine, but I'm having trouble (or am I?) with the way completion works. Consider the example:
1) I invoke completion (
|
is the position of the cursor I send withCompletionParams.Position
):and get all kinds of relevant stuff, starting with
accessKey
, and including thetextContent
.2) Now I invoke the completion here:
and I get the very same result, not filtered or sorted by the
tex
prefix.Is it an expected behaviour? Is it LSP client's job to sort/filter the completion suggestions? Thank you!
Btw, theia-ide/typescript-language-server/ displays the same behaviour.