Prioritize commands starting with search term in results #2248
+34
−0
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
- Modified filter() function to sort visible commands after filtering - Commands that start with the search term now appear first - Commands that only contain the search term appear after - Both groups maintain alphabetical order within their group - Improves UX: searching 'set' now shows SET, SETEX, SETNX first - Previously all matching commands (RESET, GETSET, etc.) were mixed together This makes it much easier to find the exact command you're looking for when searching, especially for common commands like SET, GET, etc.
Contributor
andy-stark-redis
approved these changes
Oct 16, 2025
Contributor
andy-stark-redis
left a comment
andy-stark-redis
left a comment
There was a problem hiding this comment.
Definitely more intuitive. J'approve!
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.
This makes it much easier to find the exact command you're looking for when searching, especially for common commands like SET, GET, etc.