Context provides a way to pass data through the component tree without having to pass props down manually at every level.
Why might we use Context?
Context is designed to share data that can be considered “global” for a tree of React components, such as the current authenticated user, theme, or preferred language.
Why should we use it sparingly?
Apply it sparingly because it makes component reuse more difficult.
Consume content from (at least) two of the Awesome React Context links. Share your take-away from each:
Takeaway 1: What’s new in React 16.3 Strict mode is a new way to make sure your code is following the best practices. It’s a component available under React.StrictMode and can be added to your application tree or subtree.
Takeaway 2: React’s new context API: toggle between local and global state Not all premature optimizations are the root of all evil. You should find a good balance between simplicity and scalability. That is, you should pursue simple implementations, specially if you’re building small applications. But, if you’re planning to grow, you should look for simple implementations that are also easy to scale.
Additional Questions
Looking ahead at this module’s course schedule, What do you look forward to learning?
Context API, cookies, RBAC, and all the code challenges that are to come this week
What are your learning goals after reading and reviewing the class README?
Stengethening my front end skills with these next few weeks and then combining all the information we learned in this course to build out a fully fleshed and functional applicatino with my new full-stack development skills.