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 Authentication (2019) React Router and Authentication Implement User Sign Out

Posted by Joseph Lander
.a{fill-rule:evenodd;}techdegree seal-36
Joseph Lander
Full Stack JavaScript Techdegree Graduate 27,765 Points

Ah! Wish I had known this for project 7. How could you do this without using more modern techniques?

This is a flashback moment for me as, during project 7, I needed to implement a state change in a component that felt like a brute force move and as this section suggests, React slapped my wrist and let me off with a warning.

My question is, using this example in the exercise, is there a way that you could refactor, so you didn't need to use hooks?

Otherwise, my thoughts are:

  • The warnings don't show in older versions of React so it's not a problem to be solved and there isn't a method.
  • The introduction of Hooks coincides with the warnings appearing, now there is actually a way to prevent it.
  • Perhaps, the way to refactor to prevent this issue is so verbose that people were just prepared to be careful not to introduce bugs.