-
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 trigger autorefresh when autofetch false #30405
Conversation
Pinging @elastic/kibana-app |
@@ -127,8 +127,6 @@ export class EmbeddedVisualizeHandler { | |||
forceFetch: false, | |||
}; | |||
|
|||
this.autoFetch = !(autoFetch === false); |
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 used a default value up, to make that a bit better readable.
💚 Build Succeeded |
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.
This LGTM. Could use some tests, but as discussed, we will cover that in #30422.
Tested locally Chrome OSX, compared to master, verified fixed 🚀
Merging/backporting now so I can update #30167 accordingly. |
Summary
Fixes #30347
Discover used the
visualize_loader
but setautoFetch: false
, to prevent it auto fetching the data. That flag usually mean you want to manually callrender
, etc. so I extended that flag to also prevent theautoRefreshFetch
of the timepicker to trigger a fetch/render, since that failed on Discover since there was no valid vis configuration to actually fetch the data, since it's passed in directly into therender
method by the Discover app.Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.[ ] This was checked for cross-browser compatibility, including a check against IE11[ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support[ ] Documentation was added for features that require explanation or tutorials[ ] Unit or functional tests were updated or added to match the most common scenarios[ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers
[ ] This was checked for breaking API changes and was labeled appropriately[ ] This includes a feature addition or change that requires a release note and was labeled appropriately