-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Don't have the '*' in the search bar by default #10272
Comments
Hmmm I dunno. It would speed up the initial Discover page load and allow users to see the help text that's displayed when no results are found. But it might be quite common to want to see your most recent documents, which Discover will show you by default. What do you think @tbragin @lukasolson @weltenwort ? #7238 would help mitigate this issue, but it is worth considering whether we should change the "default default" so to speak. |
A blank search bar in Kibana now acts the same as a ''. So why not just leave it that way? When you load discover/dashboard/visualization, you get the "" behavior but it just doesn't show a '*' in the search bar. I think I even found the place that needs to be changed in the parseQuery directive. I'll have a pull request here shortly to hide the '*'. |
Though now that I look at it, there doesn't appear to be a way to save a search that does not have a *, so maybe that's not a good solution. I suppose that is what this comment refers to #10272 (comment) @trevan Do you want the initial load of Discover to still return the results even though the search bar has no "*"? Or to not perform any query at all, and show some sort of help text? I thought it was the former from reading your original ticket, but @Bargs reaction seems to imply the latter. |
I want the former. A blank search bar is already equivalent to an asterisk. So instead of showing the asterisk, just use blank. |
@Bargs, I just created the pull request. |
Without the '*' in the search bar, the bar will show the placeholder text of "Search...". That makes it more discovererable. I've had several users can't figure out where to type in their search query because of this.
In addition, I've also had a few users type in their search without removing the asterisk. So instead of an easy query of "snow", they are running a regex query of "*snow".
The text was updated successfully, but these errors were encountered: