Skip to content

Quick open file order does not make sense as designed #92282

@mattaningram

Description

@mattaningram

image

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

Metadata

Metadata

Assignees

Labels

*duplicateIssue identified as a duplicate of another issue(s)quick-pickQuick-pick widget issues

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions