Skip to content
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

Global search bar - displays 'index pattern' instead of 'data view' #119410

Closed
mattkime opened this issue Nov 23, 2021 · 4 comments · Fixed by #119442
Closed

Global search bar - displays 'index pattern' instead of 'data view' #119410

mattkime opened this issue Nov 23, 2021 · 4 comments · Fixed by #119442
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Navigational Search Global search bar Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0 v8.1.0

Comments

@mattkime
Copy link
Contributor

mattkime commented Nov 23, 2021

Two issues - both the display of the item AND the string used to find it type:index-pattern -

Screen Shot 2021-11-22 at 5 27 36 PM

...and the docs need to be updated accordingly, depending upon how this is resolved -

Screen Shot 2021-11-22 at 2 46 52 PM

>
@mattkime mattkime added bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0 Feature:Navigational Search Global search bar v8.1.0 labels Nov 23, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@pgayvallet
Copy link
Contributor

We need to use the management.displayName property that was introduced in #113091, instead of type.name

@pgayvallet pgayvallet self-assigned this Nov 23, 2021
@pgayvallet
Copy link
Contributor

pgayvallet commented Nov 23, 2021

So, fixing the displayed label is quite easy. However regarding the search term, the fact that the displayName of index-pattern has a space in it (data view) makes searching by this type slightly more complicated for the user, as he's forced to escape with double quotes:

Screenshot 2021-11-23 at 11 36 06

However to be honest, I can't really do better without introducing further hacky logic in the result provider. Types are expected to be exact matches, and I quite don't like the idea of changing this. (also note that searching by type:index-pattern would still work, I'm allowing both)

@mattkime does this forced escaping seem acceptable to you?

@pgayvallet
Copy link
Contributor

nm, we're already doing lower-case conversion during the matching, I guess replacing with - is acceptable. User will then be able to search using type:data-view

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Navigational Search Global search bar Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0 v8.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants