Add fuzzy score boosting for usage frequency #43899
Draft
+143
−18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cla-bot
bot
added
the
cla-signed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a boost field to StringMatchCandidate that multiplies fuzzy match scores. Command palette uses this to rank frequently-used commands higher in search results.
Uses square root scaling (1 use → 2.5x, 10 uses → 5.74x, 50 uses → 11.6x) so frequent commands get advantage without completely overriding fuzzy match quality. Zero-score matches stay filtered out regardless of boost.
Includes tests verifying boost works with empty queries, affects ranking, and doesn't promote non-matches.
Alternative approach to #30386