fix(raf-state): accumulate updates passed between repaints #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, updates scheduled via
useRafStateare deferred to the next frame, canceling previously scheduled update. If multiple function updates (e.g.setState(prev => prev + 1)) occur between repaint cycles, only the last update is executed, and previous intermediate state transitions are lost.In the demo, the
doublecallback should increment the counter twice by callingsetCount((v) => v + 1)two times. However, only the last call is actually executed on the repaint, so instead of resulting in+2, it results in+1.What was changed
useRafStateto accumulate state changes and only set the final state value on repaint (next frame)