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
From pKdGS-181-p2 - In old stats, a timestamp at the top of the page denoted the time that the stats displayed on the page were last updated. At one point early in Calypso Stats, we attempted to re-create a similar timestamp on stats pages, but due to the various stats-lists and dozens of render()s on a stats page, it proved difficult.
We currently do not track the time each state/stats/list tree was last updated, but perhaps we could implement some tracking in the state tree level, or maybe track changes of the data in a state variable in connected-list?
@youknowriad any thoughts on the best way to track this?
Some of the user requests are specifically around the chart data, so perhaps we could start there.
The text was updated successfully, but these errors were encountered:
Yep, we could definitely track the last requested date on the state tree by stat query I guess.
But sometimes there are different components (Queries) on the same page, that would make it a bit difficult to show a timestamp by page.
From pKdGS-181-p2 - In old stats, a timestamp at the top of the page denoted the time that the stats displayed on the page were last updated. At one point early in Calypso Stats, we attempted to re-create a similar timestamp on stats pages, but due to the various stats-lists and dozens of
render()
s on a stats page, it proved difficult.We currently do not track the time each
state/stats/list
tree was last updated, but perhaps we could implement some tracking in the state tree level, or maybe track changes of the data in a state variable inconnected-list
?@youknowriad any thoughts on the best way to track this?
Some of the user requests are specifically around the chart data, so perhaps we could start there.
The text was updated successfully, but these errors were encountered: