Class names showing after non-existent properties (named suggestions).

[ghost]

Hello and thanks for making this extension, it's very helpful. There is one small bug that I can see.

When initiating autocomplete, the class names are showing after non-existent property names. You can see in this screenshot:

On a plain object in the same file, you can see that the properties are listed in the correct order:

Is there anything that I can do to fix this?

My VS Code info:

Version: 1.66.1
Commit: 8dfae7a5cd50421d10cd99cb873990460525a898
Date: 2022-04-06T14:51:26.173Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.4.184-1-MANJARO

[ghost]

The one thing that worked for me was to disable named suggestions entirely, in VS Code settings:

"javascript.suggest.names": false,

Unfortunately, I would prefer to keep that setting enabled.

[ghost]

Trying to solve this problem myself, I was lead to VS Code microsoft/vscode#21611

via the following StackOverflow answer:

See this comment of an open VS Code issue.

When your CompletionProvider was registered using a DocumentSelector that is more significant than that of other providers and returns at least one completion item, the other providers are skipped.
The word-based suggestions provider is less significant and so it does not contribute any suggestions.

Depending on the nature of your extension you could try to define a less specific DocumentSelector when registering your CompletionProvider.
If this is not possible I think there is no other option than to providing all completion items yourself (including word-based suggestions).

But I'm a little out of my depth as I don't have much experience using the VS Code API, so I'm just leaving my notes here.

[iChenLei]

@waynebloss Thanks for your sharing, it's useful for us to improve extension's ux