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.
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.