Thinking in React: Static Versions
The course is part of this learning path
This module looks at static versions in React, Props, and Mock Components to use when testing an application.
The objectives of this module are to provide you with an understanding of:
- How to be able to build a static version of an application
- How to use Props in components
- How to be able to test Component snapshots and Components with props
- How to be able to Mock components when testing
This learning path is aimed at all who wish to learn how to use the ReactJS framework.
Prerequisites of the Course
We welcome all feedback and suggestions - please contact us at firstname.lastname@example.org to let us know what you think.
Once we have the component hierarchy outlined, we can build a version that takes our data model and renders it without interactivity. Decoupling the view and interactivity is good, as static versions are lots of typing and little thinking and vice versa. The established best practice is to build components that reuse other components and pass data using props. We won't be using state here, because that is used for interactivity. A top-down approach to building our components is as acceptable as a bottom-up approach. Although this bottom-up approach is more common in TDD environments. Doing all this helps to establish a library of reusable components to render each data model from. Each component only has a return JSX expression and any minimal logic to help create it. To effectively do this you need to understand what props are, and the mechanisms that are used to pass props down the component tree. It would also be handy to know about default props, and how you can type safe invalidate props and components using prop types. If you're not familiar with these ideas, I suggest leveling up your skills on props using our lining materials before continuing with the thinking in React track.