You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using file fuzzy search I regularly get unexpected search results. Illustrative example:
In the above image, the search was for cartenums. The top match is for a file that contains all those letters, in that order, however the next 6 results contain all those letters, in that order, closely together, in what are clearly more relevant files to any human reading the list of results.
For some context which may or may not be useful, this repository is a web app that contains both a large frontend and a large backend codebase. In the file listing, all frontend files are alphabetically before all the backend files. Anecdotally, it seems that the issue only happens this way around.
If I were to guess about the source of the issue, it would be that the search algorithm does not weight results with characters in groups higher than those that just contain the characters in order, however it may be that it does do this and that the weighting is just not at the level needed for my particular use.
I'm happy to help work on this and contribute a fix if I can have some pointers towards where to look and/or the go-ahead that a fix would be wanted. My idea would be to implement this weighting mentioned above in some form.
VS Code version: Code 1.62.3 (ccbaa2d, 2021-11-17T07:59:13.865Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz (8 x 2700)
Yeah this is because the first item in your quick pick contains all of the letters inside of the name of the file while the other items don't - they have all of the letters inside the full path. This is a dupe of #25925
Issue Type: Bug
When using file fuzzy search I regularly get unexpected search results. Illustrative example:
In the above image, the search was for
cartenums
. The top match is for a file that contains all those letters, in that order, however the next 6 results contain all those letters, in that order, closely together, in what are clearly more relevant files to any human reading the list of results.For some context which may or may not be useful, this repository is a web app that contains both a large frontend and a large backend codebase. In the file listing, all frontend files are alphabetically before all the backend files. Anecdotally, it seems that the issue only happens this way around.
If I were to guess about the source of the issue, it would be that the search algorithm does not weight results with characters in groups higher than those that just contain the characters in order, however it may be that it does do this and that the weighting is just not at the level needed for my particular use.
I'm happy to help work on this and contribute a fix if I can have some pointers towards where to look and/or the go-ahead that a fix would be wanted. My idea would be to implement this weighting mentioned above in some form.
VS Code version: Code 1.62.3 (ccbaa2d, 2021-11-17T07:59:13.865Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No
System Info
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (70)
(9 theme extensions excluded)
The text was updated successfully, but these errors were encountered: