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
Fixed bug in the filters of flyouts #2935
Fixed bug in the filters of flyouts #2935
Conversation
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.
LGTM!
Checked works properly
@@ -108,7 +108,7 @@ export const Discover = compose( | |||
constructor(props) { | |||
super(props); | |||
this.KibanaServices = getDataPlugin(); | |||
this.filterManager = props.shareFilterManager ? this.KibanaServices.query.filterManager : new FilterManager(getUiSettings); | |||
this.filterManager = props.shareFilterManager ? this.KibanaServices.query.filterManager : this.KibanaServices.query.filterManager; |
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.
Here, this.filterManager
always has the same value, don't?
Why not, simplify to:
this.filterManager = this.Kibanaservices.query.filerManager
I tested the PR and it is working! |
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.
I tested it the filters are applied but are using the same Filter manager instance that the kibana discover search bar, it is not expected behavior.
I proceed to change it.
…n-Regulatory-Compliance-and-Mitre
…n-Regulatory-Compliance-and-Mitre
Hello team, we have resolved a bug that did not allow us to use filters in both Miter flyouts and Regulatory Compliance tables.
Closes. #2895.