-
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
[Lens] Fix bugs in Lens filters #56441
[Lens] Fix bugs in Lens filters #56441
Conversation
Pinging @elastic/kibana-app (Team:KibanaApp) |
I'm going to update this PR to fix another bug: #55603 |
@elasticmachine merge upstream |
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.
Tested on Chrome Linux, LGTM. Code LGTM. Found another issue with filters, but I think it's out of the scope of this PR, so I'll open a separate issue for it.
Follow up issue: #56627 |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
* [Lens] Fix bug where filters were not displayed * Fix elastic#55603 Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* [Lens] Fix bugs in Lens filters (#56441) * [Lens] Fix bug where filters were not displayed * Fix #55603 Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> * Fix bugs * Update * Actually fix infinite loop due to referential equality * Update snapshot * Build filters explicitly Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Release note
Fixes bugs in Lens display of filters. When navigating to Lens from a dashboard, only pinned filters are used now. Also, when navigating to a previously-saved Lens visualization, Lens now shows all of the filters that were saved with the visualization. Now Lens is accurately showing all saved filters.
Notes
Fixes #54941 and fixes #55603
The bugs are caused by a change to the TopNav component, previously filters were displayed based on Lens's internal state, but now use the
filterManager
component. We did not write code to callsetAppFilters
on the filter manager at the appropriate times.Steps to verify #55603:
Steps to verify #54941:
2. Refresh the page