If you’re not too sure on how to get TypeScript working with Facebook’s boilerplate, you can quickly check out another post of mine here and just work your way through the part that deals with this initial setup step and removing the boilerplate code that we won’t need.įor styling purposes I’ll be using styled-components and reactstrap, validator for input validation and uuid to generate unique id’s. I’ll be using create-react-app with TypeScript for this exercise. I had the privilege of sharing this post in presentation format at the virtual version of ReactEurope 2020, if you’re keen to watch the video walk-through, go ahead and check out the video below. If you enjoy the post, feel free to buy me a coffee here ☕️ 😃. I wouldn’t say this approach is better, but if you’re like me and you prefer to delve into building a small app that demonstrates as well as explains what you’re learning, then this one is for you 😉.
The aim of this post is to provide developers with an alternative to the other guidelines that are out there. I should say this from the onset, there are a ton articles and tutorials on understanding React Hooks, and most of the one’s I’ve come across are really good. I think it’s still good to have a pattern whereby we have container components that have our business logic and presentation components that have the responsibility of UI presentation. That being said, not every function component you write has to make use of Hooks. With Hooks, function components can be used to manage state, make use of a component’s lifecycle events, as well as connect to the context of React apps.Īs a result, our function components are going to be a little more complex than what we may be used to.
Features that were previously exclusive to class based components can now be utilised with function components. Learning React Hooks can be a little bit intimidating because it’s a different way of working with components.
0 kommentar(er)
