You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add unified state change observables to query service, to replace existing callbacks (ATM we use a mix of observables for filters and timefilter and refresh interval and callbacks for query and saved query.
data.query.getStateChanged$() will trigger when time, filters, query, auto-refresh or saved query values change, with an object with the full current state. Note: this doesn't necessarily mean data has to be re-fetched. For example, changing a disabled filter or stopping automatic refresh.
data.query.getFetch$() will trigger when a setting that requires fetching data changes. It should also trigger when a user clicks on the refresh button, without any state changes.
I also opened this one before which is related: #56503
The difference is, that in the moment we have to have helpers which observe separately for things that fall into AppState and into GlobalState
Add unified state change observables to query service, to replace existing callbacks (ATM we use a mix of observables for filters and timefilter and refresh interval and callbacks for query and saved query.
data.query.getStateChanged$()
will trigger when time, filters, query, auto-refresh or saved query values change, with an object with the full current state.Note: this doesn't necessarily mean data has to be re-fetched. For example, changing a disabled filter or stopping automatic refresh.
data.query.getFetch$()
will trigger when a setting that requires fetching data changes. It should also trigger when a user clicks on the refresh button, without any state changes.So a common application pattern would be:
Tasks
The text was updated successfully, but these errors were encountered: