-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: Throttle state serialization #15266
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: main
Are you sure you want to change the base?
Conversation
The storage write debounce has been replaced with the `redux-persist` option `throttle`. This option has the advantage of applying to state serialization as well as writing, so we avoid frequent expensive serialization. Using `throttle` instead of `debounce` also guarantees a write every so often during periods of rapid state updates, ensuring the application doesn't go too long without persisting.
|
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.
Platform code LGTM, agreed with @Prithpal-Sooriya . let's rename it to be throttle
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
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
|
|
|
The storage write debounce has been replaced with the
redux-persist
optionthrottle
. This option has the advantage of applying to state serialization as well as writing, so we avoid frequent expensive serialization. Usingthrottle
instead ofdebounce
also guarantees a write every so often during periods of rapid state updates, ensuring the application doesn't go too long without persisting.Description
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist