-
Notifications
You must be signed in to change notification settings - Fork 2k
fix: trigger recalculation when snapshots change #40772
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
base: fix/prog-safer
Are you sure you want to change the base?
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
Size Change: 0 B Total Size: 3.34 MB ℹ️ View Unchanged
|
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.
1 file reviewed, 2 comments
aafd660 to
e5b06f4
Compare
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
|
📸 UI snapshots have been updated3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
Triggered by this commit. |
|
📸 UI snapshots have been updated3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
Triggered by this commit. |
|
1 similar comment
|

this was very 🤯 for me
we had aggressively cached the snapshot data because the processing is so heavy on the browser
it would only be recreated when we polled the full listing snapshots after we'd loaded all data
this was fine when we weren't playing until we had loaded all the data
but, the better i made progressive loading, the less often we polled full data, and the longer the gap between loading some data and it being available to the player
to keep the processing cheap we keep the count of successful API calls on the cached object and recreate the object instance when that changes so that downstream selectors recalculate
(in theory that's not necessary, but in practice it was firing more and the browser was thrashing unnecessarily)
[uploading 2025-11-01 20.07.40.gif...]