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
Hi @vince-fugnitto, may I ask you (as you authored #9928) to update the filterItems function to fix the next problem (focus on the bold letters),
this causes the search order to be unsorted because it put down items that need to be upper:
on theia:
may I ask you (as you authored #9928) to update the filterItems function to fix the next problem (focus on the bold letters).
@EstherPerelman I don't plan on revisiting the search at this time, if you have an improvement then please go ahead. The use-case you described is also not so critical, the result still displays it is just that fuzzy matching is more eager than matching the whole word, and results are still sorted (alphabetically).
this causes the search order to be unsorted because it put down items that need to be upper.
The search order for commands is always alphabetical, the fuzzy just helps us match results.
Bug Description:
Following #9154,
fuzzy
searching is broken in thequick-input
orquick-service
.Steps to Reproduce:
theia
as a workspace folder.ag
- notice that only results that have exactlyag
as a substring are present.fuzzy.mp4
The following is valid with fuzzy:
The text was updated successfully, but these errors were encountered: