editor.suggest.matchOnWordStartOnly:true not working correctly

[mboeker]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.93.1
• OS Version: Windows 10

I have editor.suggest.matchOnWordStartOnly:true set. Somewhere in my project I defined the string splunk_targetUri Now every time I type the last letter "e" in "true" it autosuggests "splunk_targetUri"

Steps to Reproduce:

1. Somewhere in your project define something that contains the letters t, r, u, e (anywhere in the name, in order)
2. In a new document, type "true"
3. Popup appears suggesting the string you defined in step 1.

Expected behavior:

• If I have defined splunk_targetUri in my project, then go ahead and suggest it if I type "splunk_" or something similar
• If I have defined "true_sometimes" in my project, then go ahead and suggest that if I type "true"
• Don't suggest random strings just because somewhere in there they have the same letters

[vs-code-engineering[bot]]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.100.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[jrieken]

This is what the docs for this setting say:

When enabled IntelliSense filtering requires that the first character matches on a word start. For example, c on Console or WebContext but not on description. When disabled IntelliSense will show more results but still sorts them by match quality.

So, the target-subword of splunk_targetUri is considered a word start and therefore matched by true

[slztfn]

Is there any way to improve/control the "sorts them by match quality"?

With matchOnWordStartOnly:false I expect to see symbols from the current scope that match not just on the start of the word. You can see how it matches on word start a symbol from current scope and ignores the partially matching symbols and shows instead a long list imports