← Back to Lessons
Edit on Github

Global state with the Context API

The problem, or "why life before the Context API was harder"

People say that React.js makes the easy stuff hard and the hard stuff easy. It's funny, because it's true 😓. These are some of the things they mean:

  1. Why is it so hard to share data throughout the entire application? Where are my global variables?
  2. Why is it so hard to pass data between components? A.K.A props. Props are fine when you want to pass data between parent and child, but what happens when we need to go deeper? This is called "Props Hell" or "Prop Drilling".
  3. Redux (https://redux.js.org/)?? Overkill.

The Context API is here to solve some of those conundrums by:

  1. Centralizing a global application state: Instead of being limited to local states on views, you can now share data on one central component and spread to its inner components (children, grandchildren and so forth). The centralized state is called store and we can spread it by using the Context.Provider and Context.Consumer

  2. Data propagation and re-rendering: when this centralized global state (store) changes, it triggers a re-render of all of the children compoments (your entire application) which produces new data to show up in the UI. A central setState*ish*.

  3. If you've already worked with react, you've probably felt the frustration of passing properties throughout your application, we call it "property hell".

How does the Context API work?

The concept behind it is very simple: There is one big Provider, that provide the data to many Consumers, there's no limit in the amount of consumers you can use.

Every time the data stored within the Provider changes, all the Consumers update. It is very similar to how TV signal works: TV channels emit a data signal and all TV antennas consume this signal, receiveing the new content and rendering the image on the televisions.

Everyone has access to the global context now.

Context API Explanation

Unidirectional data flow

The store is now the most delicate piece of data in our application, and it is succeptible to bad usage, i.e. one bad change and the whole application will crash. To avoid this possible scenario we have to make sure the store's data is read-only for the consumers, and can be updated anew by a limited set of functions. Just like the regular state, we don't change the state, we set it anew. This architecture paradigm is called Flux.


In-Depth Overview of Flux Architecture

We must split the store from the actions and the views (components) and make sure that the views call actions to update the store. We will never directly change the store from a view. I know, I'm being redundant on purpose...

Now everything together

  • We're going to implement a single point of truth for the whole react application: global state.
  • This state will contain the data and functions to set the new state: store and actions .
  • We're going to deliver it throughout the whole application using the context: Context.Provider and Context.Consumer (if using classes as React components) or useContext() hook (if using functions as React components)

Simple implementation

  • Step 1 (Create the context): This step has almost no logic, just call the createContext function from react. That object will be shared within all the consumers during the application lifetime, it will contain the application store and actions.


// Step 1: define a context that will be shared within all the app. import React from 'react'; const AppContext = React.createContext(null);
  • Step 2 (Store and Actions): Create a ContextWrapper component which will be used to pass the context (step 1) to the Consumers. The ContextWrapper's state is where we declare our initial global state, which includes the data/Store store and the functions actions. Note that we have to export both the AppContext and the ContextWrapper.


// Step 2: Create a ContextWrapper component that has to be the parent of every consumer. import React from 'react'; export const AppContext = React.createContext(null); export const ContextWrapper = (props) => { const [ store, setStore ] = useState({ todos: ["Make the bed", "Take out the trash"] }); const [ actions, setActions ] = useState({ addTask: title => setStore({ ...store, todos: store.todos.concat(title) }) }); return ( <AppContext.Provider value={{ store, actions }}> {props.children} </AppContext.Provider> ); }
  • Step 3 (Views): Now your main component can be wrapped inside ContextWrapper so that all children components will have access to the Context. For this quick example we will be using the <TodoList /> component as our main component (the declaration is on the last step).


// Step 3: Wrap your main component in the ContextWrapper, import React from 'react'; import { ContextWrapper } from 'path/to/AppContext.js'; const MyView = () => ( <ContextWrapper> <TodoList /> </ContextWrapper> ); ReactDOM.render(<MyView />, document.querySelector("#app"));
  • Step 4: Now we can create the TodoList component knowing that we can use the Context.Consumer (in classes) or useContext() hook (in functions) to read the store from the global state (no props necessary).

    In this case the component will render the to-do's and also be able to add new tasks to the list.

// Step 4: Add the Context.Consumer tag to any component import React, { useContext } from 'react'; import { AppContext } from 'path/to/AppContext.js'; export const TodoList = () => { const context = useContext(AppContext); return <div> {context.store.todos.map((task, i) => (<li>{task}</li>))} <button onClick={() => context.actions.addTask("I am the task " + context.todos.length)}> + add </button> </div> }

Very often we will use the hook that you see above

const context = useContext(AppContext); return <div> {context.store.todos.map((task, i) => (<li>{task}</li>))} <button onClick={() => context.actions.addTask("I am the task " + context.todos.length)}> + add </button> </div>

in its destructured variant. Pay attention how that also simplifies the way we then access the store:

const {store, actions} = useContext(AppContext); return <div> {store.todos.map((task, i) => (<li>{task}</li>))} <button onClick={() => actions.addTask("I am the task " + context.todos.length)}> + add </button> </div>

Test the code live

Subscribe for more!






The most efficient way to learn: Join a cohort with classmates like yourself, live streamings, coding jam sessions, live mentorships with real experts and keep the motivation.


From zero to getting paid as a developer, learn the skills of the present and future. Boost your professional career and get hired by a tech company.


Start a career in data science and analytics. A hands-on approach with interactive exercises, chat support, and access to mentorships.


Keep your motivation with this 30 day challenge. Join hundreds of other developers coding a little every day.


Start with Python and Data Science, Machine Learning, Deep Learning and maintaining a production environment in A.I.

©4Geeks Academy LLC 2019

Privacy policies

Cookies policies

Terms & Conditions