Skip to content
This repository was archived by the owner on Oct 16, 2020. It is now read-only.
This repository was archived by the owner on Oct 16, 2020. It is now read-only.

Completion not filtering/sorting by prefix #630

@brainoutsource

Description

@brainoutsource

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 with CompletionParams.Position):
document.body.|textContent = user; 

and get all kinds of relevant stuff, starting with accessKey, and including the textContent.

  1. 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.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions