Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript React Components (2018) Stateful Components and Lifecycle Methods Update the Stopwatch State with componentDidMount()

Brian Hoang
Brian Hoang
11,515 Points

setState in handleStopwatch()

The fact that in the video "!this.state.isRunning" is evaluated to "true" and console logs "starting..." the first time Guil clicks the start button implies that the isRunning state was not changed by setState before the "if(!this.state.isRunning)" line

Should I from now on assume the effect of setState method is not immediate, at least in the function it was called?

1 Answer

Zaberca David
Zaberca David
2,965 Points

This is the same thing I was wondering about. At 4:33, the instructor says 'only when starting the timer'. In concept, when the timer starts, the isRunning flag goes from false, to true. The if statement condition here is (!this.state.isRunning), which goes true when isRunning is set to false. That means the previous setState method did not change the state.

Can somebody confirm this and maybe explain further or give some references? Thank you

Zaberca David
Zaberca David
2,965 Points

Ok, so I researched further and found the answer. It seems that since setState is an async function, and async function are put into event loop and always executed after the call stack is cleared, it is guaranteed that the this.state.isRunning will be false for the entirety of the handleStopWatch.