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()

Begana Choi
PLUS
Begana Choi
Courses Plus Student 13,126 Points
Posted by Begana Choi
Begana Choi
Courses Plus Student 13,126 Points

why don't we use prevState in tick function for ( now - this.state.previousTime )?

prevState is the better way to verify that state did update correctly. but why we don't use prevState for this part?

tick = () => {
        if(this.state.isRunning){
            const now = Date.now();
            this.setState( prevState => ({
                previousTime: now,
                elapsedTime: prevState.elapsedTime + ( now - this.state.previousTime ) <<this part
            }))
        }
    }

1 Answer

Mia Filisch
Mia Filisch
16,117 Points
Mia Filisch
Mia Filisch
16,117 Points

I was just wondering the same thing! My understanding is that it's always better to use prevState than this.state when updating state based on existing state, so I assume this is simply an oversight. I used prevState in both places and it seems to work fine!