-
Notifications
You must be signed in to change notification settings - Fork 29.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the sorting and matching of quick pick #14879
Comments
@kentcdodds is this about general sorting in all quick open things like file search, command search etc. or only for extensions that use the picker widget? |
I think that the way match-sorter works too improve the intuitiveness of lost filtering and matching is actually pretty great, so it probably makes sense for everything. |
Makes sense. |
@bpasero, When I asked @kentcdodds to fill an issue here, I didn't remember the other issue that already existed, so it could be linked. I did another search and found, it's #14727. Since you were looking for a better fuzzy search, I thought you could work together on this. Hope this helps |
Yup, they are related. I am however currently not working on it (I unassigned myself). Sorry for the confusion. |
Here's an example of where it goes wrong: The file The solution is to score in a way that promotes results with a low distance between each character. Levenshtein would work here. |
Yeah, there's an issue right now for adding something like that to |
/duplicate #34088 |
This issue has been closed because it is already tracked by another issue. See also our GitHub issues to search for existing issues and our issue reporting guidelines. Happy Coding! |
Originally posted in the
vscode-project-manager
extension issues here. @alefragnani suggested that I file the issue here to have this applied toPickList
. I'm unfamiliar with this codebase. But I think thatmatch-sorter
provides a better way to filter and sort items in a list based on user input. Could we consider adding that kind of functionality to VSCode?Thanks!
The text was updated successfully, but these errors were encountered: