Skip to content

Commit 2b62244

Browse files
committed
docs(README.md): mention no batching callbacks
1 parent 08d2fc7 commit 2b62244

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ export default App;
9797

9898
* When a state update is called with the current value and optimized away, the callback is never called.
9999
* `useStateWithCallbackLazy` calls the callback with the scope that existed before update, while this.setState callback can access the updated this.state and `get something()` computed values. This can't be fixed, but it's a problem for people who expect a drop-in replacement.
100-
100+
* When `useStateWithCallbackLazy` state is updated several times with batching (e.g. in an event handler), only the last update calls the callback.
101101

102102
## Contribute
103103

0 commit comments

Comments
 (0)