Read 33 ~ Context API
By Abdallah obaid
NAME | URL |
---|---|
Home | Home. |
Prep | Prep: Engineering Topics. |
Read 01 | Node Ecosystem, TDD, CI/CD. |
Read 02 | Classes, Inheritance, Functional. |
Read 03 | Data Modeling & NoSQL Databases. |
Read 04 | Advanced Mongo/Mongoose. |
Read 05 | Linked Lists. |
Read 06 | HTTP and REST. |
Read 07 | Express. |
Read 08 | Express Routing & Connected API. |
Read 09 | API Server. |
Read 10 | Stacks and Queues. |
Read 11 | Authentication. |
Read 12 | OAuth. |
Read 13 | Bearer Authorization. |
Read 14 | Access Control (ACL). |
Read 15 | Trees. |
Read 16 | Event Driven Applications. |
Read 17 | TCP Servers. |
Read 18 | Socket.io. |
Read 19 | Message Queues. |
Read 26 | Component Based UI. |
Read 27 | React Testing and Deployment. |
Read 28 | Props and State. |
Read 29 | Component Composition. |
Read 30 | Hash Tables. |
Read 31 | Hooks API. |
Read 32 | Custom Hooks. |
Read 33 | Context API. |
Context API
## Context:
- Allows us to pass data, state and functions from Provider/Consumer .
- Context provides a way to pass data through the component tree without having to pass props down manually at every level.
- Context provides a way to share values like these between components without having to explicitly pass a prop through every level of the tree.
- 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.
- Context is primarily used when some data needs to be accessible by many components at different nesting levels.
- If you only want to avoid passing some props through many levels, component composition is often a simpler solution than context.