Generic fuzzy search #1584
Merged
Generic fuzzy search #1584
Conversation
This file contains 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
The other branch had weird merge conflicts so I was simpler to just make a new branch instead of fixing them.
tom-ludwig
requested review from
thecoolwinter,
Wouter01,
matthijseikelenboom,
austincondiff and
0xWDG
EstebanBorai
approved these changes
Feb 5, 2024
matthijseikelenboom
approved these changes
Feb 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR introduces a new fuzzy search algorithm that should deliver better results and better performance.
I've added the new algorithm to the open quickly overlay for now and not yet to the Settings. The reason is, the settings are a bit confusing as they are, the lack of documentation, confusing function and class names. I'm thinking of cleaning them up in a separate PR.
Related Issues
Checklist