Improve search result by prioritizing exact matches #1433
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
|
🚀 Preview deployment available at: https://dcca3028.rdoc-6cd.pages.dev (commit: b3dcacc) |
vinistock
reviewed
Oct 14, 2025
When searching for a class name like "String", the search should return exact matches first before returning classes that contain the search term in their name (like "Prism::StringNode"). This adds a new pass 0 to the search algorithm that only matches when the searchIndex exactly equals the query. The previous passes are shifted accordingly: - Pass 0: exact match (new) - Pass 1: searchIndex starts with query (was pass 0) - Pass 2: longSearchIndex starts with query (was pass 1) - Pass 3: searchIndex contains query (was pass 2) - Pass 4: regexp match (was pass 3) Fixes #1194
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.
I know adding 2 new phases for exact matches feels like a workaround, but without a more thorough review on the entire searching algorithm this is the best solution I have.
I also added basic tests for
search.jsusingmini_racergem (dev dependency) to simulate JS evaluation. I chose this approach because it should be simpler than maintaining a whole set of JS dependencies and setups.Fixes #1194