You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find the new sorting in IntelliSense quite bad for settings where I typically do not think about camel case matching but rather the name of the setting in words:
The most relevant entries when I type "close" for me are now at the end of the list:
Stable:
Either those 2 entries should be sorted to the top or we disable fuzzy scoring for settings at least.
/cc @Microsoft/vscode for input
The text was updated successfully, but these errors were encountered:
Just to clarify sorting which is always alphabetically. Scoring is applied to select the best match as type (no resorting happens).
I agree the screen shots show unhappy cases which we should tweak. Today, we rank matches on upper-cases character or after separators (., _, etc) higher than regular lower-case matches. We should also add some sort of new-gap penalty that favours single long matches over multiple short matches
I find the new sorting in IntelliSense quite bad for settings where I typically do not think about camel case matching but rather the name of the setting in words:
The most relevant entries when I type "close" for me are now at the end of the list:
Stable:
Either those 2 entries should be sorted to the top or we disable fuzzy scoring for settings at least.
/cc @Microsoft/vscode for input
The text was updated successfully, but these errors were encountered: