Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
I'm confused why you'd use the callback when updating state? Seems like an extra step when it gave you the same results
I'm confused why you'd use the callback when updating state? Seems like an extra step when it gave you the same results without adding the extra callback.
Dylan Thunn22,658 Points
You don't technically have to it, it is just a more stable way of doing it for react, with a small app though it is probably overkill. Once you get to using hooks to update state it won't really matter.
prevState is the value of the state BEFORE the callback is fired, whereas this.state.stateName holds the value of state to be altered at the time that callback is being fired. Most of the time this won't be an issue but as React can batch render updates, sometimes if a state is being updated by a variety of methods you can get get unexpected results if your updates are iterative.
thank you :)