feat: improve fuzzy scoring for exact substring matches #285449
+9
−2
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.
Fixes #284229
Previously, the fuzzy scoring algorithm applied a penalty for every character skipped before the match started. This caused exact substring matches that appeared deep within a long string (e.g., matching "joint" in "github.copilot.chat.advanced.inlineEdits.jointCompletionsProvider") to be ranked lower than weaker fuzzy matches that appeared earlier (e.g., "json.maxItemsComputed").
This change modifies
fuzzyScoreto skip this penalty if the search pattern exists as a contiguous substring within the target word.