Hooks useContext
The Context API was introduced to allow you to pass state (and enable the state to update) across the app, without having to use props for it.
The React team suggests to stick to props if you have just a few levels of children to pass, because it’s still a much less complicated API than the Context API.
In many cases, it enables us to avoid using Redux, simplifying our apps a lot, and also learning how to use React.
How does it work?
You create a context using React.createContext()
, which returns a Context object.:
Then you create a wrapper component that returns a Provider component, and you add as children all the components from which you want to access the context:
I used Container as the name of this component because this will be a global provider. You can also create smaller contexts.
Inside a component that’s wrapped in a Provider, you use a Consumer component to make use of the context:
You can also pass functions into a Provider value, and those functions will be used by the Consumer to update the context state:
You can see this in action in this Glitch.
You can create multiple contexts, to make your state distributed across components, yet expose it and make it reachable by any component you want.
When using multiple files, you create the content in one file, and import it in all the places you use it:
This hook is used in combination with the React Context API.
In particular, this hook allows us to get the current context value:
which refers to the nearest <MyContext.Provider>
component.
Calling useContext
will also make sure the component re-renders when the context value changes.
Last updated