-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Quick Search - consider removing the space after %
for text search
#191503
Comments
I contribute to an extension the implements a FileSearchProvider onto code environments (InterSystems IRIS and relatives) where "files" whose names begin with % are common since that naming convention is used for library packages. It would be a problem for our users if an attempt to quick-open, say, %Foo.Bar.cls failed because the request was now interpreted as a TextSearchProvider quick-search instead. Pinging @isc-bsaviano for info. |
John described the concern perfectly. This will lead to a lot of confusion for our users when the FileSearchProvider and TextSearchProvider APIs are finalized (which we hope is soon!). I see how having the space is inconsistent, so is there another "symbol" character that can be used other than %? Or is there a clear way to "escape" that % so it's not a search trigger? |
How about |
You can still search for |
To quick open files that start with %, users would have to enter |
"%Foo.Bar.cls |
|
I talked to the team about this - a popular idea was to just do |
I guess it'll be tolerable for our users to have to prefix with a space if they're trying to quickopen something beginning with %. |
Since quick search is being actively refined, is there any chance of |
I have been meaning to finalize |
Thanks for the update, I'm glad to hear that they are still on your radar! |
Quick Search - consider removing the space after `%` for text search Fixes #191503
We currently require
%
and a space to use the search quick access. Although files could start with%
(noted in #189964 (comment)), we should also consider how often this would be the case.Other picks like the command palette don't have a space, so perhaps it's expected to not have a space.
The text was updated successfully, but these errors were encountered: