fix fuzzyScore boost for uppercase full match #187149
Open
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.
Changes
fuzzyScoreto not treat uppercase characters in a common prefix as gap locations.If you match
FOOagainstFOOandFOOBAR, the score againstFOOis +4 compared toFOOBAR: +2 for being a full match, and +2 because gap locations at the end of the word are only penalized -3 instead of -5. This PR fixes the latter +2. This makes the scores equal whenboostFullMatch: false.Fixes #187147