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
This has been labeled as as-designed in the past, but I cannot figure out how the above sorting makes sense or would be purposefully designed this way. Any other search functionality I have used would show items matching the full string before attempting to show fuzzy matches where the search string has been arbitrarily split up. It is extremely rare that such a fuzzy match will show me what I want.
Considering how many files in React and other JS projects are called index.js with their only differentiator being in their pathname, this would save people an enormous amount of time with every single search if this sorting could be fixed.
I would add this as a feature request, but showing this to my fellow devs and every person said this was something that frustrated them daily and felt like a bug or mistaken choice, and there are no extensions or settings to fix it, so I'm calling this a UX bug.
This could very well send me back to using Atom it has become such a frustration when working on projects where most files are index.js.
Already existing issues that cannot be commented on or added to: #66964 #66383
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered:
@roblourens It has improved a bit, but it is still promoting broken up strings in file names higher than the exact string in path names. 99% of the time I want to see the results that are closest to my exact string before seeing the fuzzy results. This is particularly useful when you don't know the exact file name and have inconsistent file naming patterns where some are index.js in a names path, while others have the relevant name in the filename itself.
For example now when I scroll down a bit in the same search as the previous screenshot, you can see how much more useful the lower results would be than the results ranked higher:
This has been labeled as
as-designed
in the past, but I cannot figure out how the above sorting makes sense or would be purposefully designed this way. Any other search functionality I have used would show items matching the full string before attempting to show fuzzy matches where the search string has been arbitrarily split up. It is extremely rare that such a fuzzy match will show me what I want.Considering how many files in React and other JS projects are called
index.js
with their only differentiator being in their pathname, this would save people an enormous amount of time with every single search if this sorting could be fixed.I would add this as a feature request, but showing this to my fellow devs and every person said this was something that frustrated them daily and felt like a bug or mistaken choice, and there are no extensions or settings to fix it, so I'm calling this a UX bug.
This could very well send me back to using Atom it has become such a frustration when working on projects where most files are
index.js
.Already existing issues that cannot be commented on or added to: #66964
#66383
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: