Jul 10, 2017 · 1 min read
Thanks for the tip!
Just to note the `setState` docs also point out a callback parameter which is also guaranteed to fire after the state change has been applied. This in my opinion is more similar to node callback style syntax.
`setState` callback (
setState(updater, callback)), either of which are guaranteed to fire after the update has been applied
This does appear to be beneficially in removing the nested callbacks if a chain of setState calls was required.