- Notifications
You must be signed in to change notification settings - Fork1.1k
fix: add support for spaces in search & enable searching by display name in templates#19552
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
Uh oh!
There was an error while loading.Please reload this page.
matifali commentedAug 26, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Can we fallback to the |
rafrdz commentedAug 26, 2025
To make sure I'm following would you like to search on That can be done. Since we would now support spaces in the search queries we'd probably need to update the |
matifali commentedAug 26, 2025
Yes |
rafrdz commentedAug 26, 2025
Sounds good! Defaulting to |
matifali commentedAug 27, 2025
Nor directly related but is it possible to stop showing Can it be a hidden default filter that's always true. If someone wants deprecated templates they can set it to |
rafrdz commentedAug 27, 2025
We could remove that from the frontend as the default query and update the query to always return Should we make a new issue for this work? |
matifali commentedAug 28, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Yes let's create a new issue. Thanks |
brettkolodny left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Personally I think the UX of our workspace search needs a bit of an improvement, but I think this is a good solution given what we've got!
Uh oh!
There was an error while loading.Please reload this page.
brettkolodny left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thank you!
1677a30 intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Summary
In this pull request we're updating search to support queries with spaces in addition to the
field:valuepattern that is currently supported.Additionally templates search now defaults to
display_name(sincedisplay_nameis optional the search will fallback toname) when searching without thefield:valuepatternCloses:#14384
Downsides with searching on
nameanddisplay_nameBecause the
namefield cannot include spaces, we end up in a situation where including a space in the query will result in no results since the query searches on bothnameANDdisplay_name. In the following example, we can see the results of searching by bothnameanddisplay_nameon these templates:name-and-display-name.mov
Proposal: Search on
display_nameby default and allow fornameusing thefield:valuepatternIf we remove
namefrom the default template search, we're now able to search with spaces on templatedisplay_names. Sincedisplay_namesare what users see in the templates list they might expect the search to work this way.Below is an example of
namebeing removed from the default template search.display-name.mov
With this approach users would still be able to search on template names by specifying
exact_name:foo.Testing
Added additional test cases to ensure spaces were handled as expected in combination with
field:valuepatterns.