-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Broken fuzzy search algorithm in picker #34914
Comments
@fabiospampinato some of this can be explained by the fact that fuzzy search is NOT enabled for the normal picker (see #34088). Currently we have it only enabled for the file search because it still needs to be tweaked. I need to check for the leading whitespace issue but it may be related to the same cause. |
@fabiospampinato trying to reproduce the issue with leading white space but I cannot: Is there any way I could try it on the code that you used for your animation to reproduce the same? |
@bpasero Try prefixing those strings with exactly 8 spaces. For whatever reason the bug doesn't manifest itself with just 4 spaces in my system. If it doesn't work, install Projects+, run {
"groups": [
{
"name": "open",
"groups": [
{
"name": "vscode",
"projects": [
{
"name": "vscode-projects-plus-todo-plus",
"path": "/"
},
{
"name": "vscode-todo-plus",
"path": "/"
}
]
}
]
}
]
} Then run It would be weird if it still doesn't work. |
@fabiospampinato thanks, I can reproduce now. |
@bpasero Here there's another bug, in the following gif I hit When will this bugs be resolved? |
@fabiospampinato I think that one is fixed already in our latest insider build, can you check |
@bpasero It's fixed. Thank you. |
/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! |
The fuzzy search algorithm can be improved to solve all problems listed in #27317, but IMHO it's completely broken and it should be rewritten from scratch. Let me show you some of the errors I've found:
Doesn't work with leading spaces
This is the expected behavior:
This is what happens if the strings have some leading spaces (useful for extensions like Projects+ for showing a tree-like structure):
Not really "fuzzy"
As I understand it, the term "fuzzy" in "fuzzy search" basically means that the characters provided in the search query can have 0 or more other arbitrary characters between them in the matching string. The current algorithm looks like regular search instead:
Overly strict about string position
For some reasons there are strings that match against some queries, but don't mach against less specific versions of those queries. I mean, a more specific query should provide the same or less results, not more, right?
The text was updated successfully, but these errors were encountered: