Click here to view part 1 in this series: Compound Components

Click here to view part 3 in this series: Render Props

In the last part of the series, we discussed how to use compound components and static class methods to produce reusable and flexible components. Using the API we created, we are able to dynamically recreate different variations of the component in a very declarative fashion.

We can easily add as many steps as we want and we can decide if we want the progress panel on the left or the right.

A simple implementation of the Stepper component

The reason we are able to this is because we used some React API helper functions to pass the desired props to each child in the tree ; the ‘stage’ and ‘handleClick’ props are accessible to the components that need them.

There is one major flaw with this technique though. Props are only able to be passed down to their direct children. This makes the API very rigid and the ‘Stepper.Steps’ component has to be a direct child of the ‘Stepper’ component otherwise it will break. This has massive implications in terms of flexibility.

What if we wanted to go a bit crazy and use a bit of flexbox magic to add a title?

By adding a simple div we completely break the component. The ‘Stepper.Steps’ component is no longer a direct child of the ‘Stepper’ component and is therefore unable to receive its props. Wouldn’t it be great to have the flexibility to add small adjustments when ever we wanted?

Context to the Rescue!!

React Context API

React Context has been around a while but React’s engineers made it very clear it was experimental and would likely break in the near future. The great news is that as of React 16.3, this is now stable and can be used throughout your React applications.

So what is this Context we keep hearing about?

I couldn’t come up with a clearer definition than the one in React’s official documentation:

Context provides a way to pass data through the component tree without having to pass props down manually at every level.

This is exactly what we need to solve our problem! Using Context, we no longer need to loop through and clone each child to pass down required props. Context is designed so that we can share ‘global’ state that can be shared anywhere in the React tree.

Using Context, all of our components have access to the ‘stage’ and ‘handleClick’ props.

So, let me guide you through the Context API, and the steps you need to take to get it up and running.

1: Create a new context

React now comes with a method called ‘createContext’. All we need to do is simply call this method and assign it to a variable.

The new context we created provides us access to a Provider and Consumer pair. The Provider, believe it or not, provides the ability for us to share state changes throughout our React Tree. The Consumer allows us to subscribe to these state changes anywhere in the tree.

2. Create Context Provider

Our Context we just created has a Static Class method called ‘Provider’ that creates a React component. This component accepts a value property. This is extremely important as it is this property that will represent our global state that we need to pass to components further down in the tree. In our case all we want to share globally is the ‘stage’ prop and ‘handleClick’ method.

By using the props.children technique that we used in the first part of this series, we can dynamically expose any child components to the Provider, regardless of how deep it is in the tree.

3. Wrap our Provider around our Stepper Component

By simply wrapping the ‘StepperProvider’ component around our original ‘Stepper’ component, any child components further down the tree now have exposure to our context.

As it stands our Stepper code looks almost identical, however by simply wrapping it in the StepperProvider component all of our child Components will have access to ‘stage’ and ‘handleClick’ without manually drilling them down to each component.

4. Refactor our components

Originally, our state was managed by the Stepper component and we cloned each child element to be able to receive the props required.

Almost all of this code is no longer required. We no longer need to create state, and we no longer need to pass down any props. We could do away with this code altogether but it’s a good place to declare our static methods to create a clean, readable API.

5. Subscribe to state changes using a Consumer

I will use the the Stepper.Step component to demonstrate how to wire up the Consumer component. Previously, the Stepper.Step component required its parent to directly pass down the stage prop in order for it to function properly:

With our application wired up with Context we no longer need this as a prop. We can use the Consumer to subscribe to it instead:

<Consumer>

{value => /* render something based on the context value */}

</Consumer>

The Consumer requires a function as a child and provides this function with our global context value. When the function is complete, it returns a react node.

What on earth does that mean?

It’s a bit of a head scratcher at first but lets take a look at the ‘consumed’ Step component.

Instead of adding the ‘Step’ markup directly as a child to the Consumer, we instead add a function. This function provides the values we created from our Provider earlier and we can then use ES6 destructuring to pull off the stage prop. The ‘Step’ component now has access to the stage prop like before but this time it is pulled from the context. from here we are free to do with it as we wish; in this case we use it to determine what React node is returned.

The technique being used here may seem a little strange. It is called render props and the official react docs explain it here. This is an extremely powerful technique that I’ll be talking about in part 3 of this series.

6. Repeat Stages 4 & 5 for all components that either require props or pass down props

I wont go into step by step detail here but by repeating stages 4 & 5 for the Stepper.Steps, Stepper.Progress and Stepper.Stage components you should end up with your component looking and functioning exactly the same as before.

None of our components are now reliant on being direct descendants of others. Boom! We now have much more flexible code and should be able to add the heading we were unable to do earlier!

The Stepper.Steps and Stepper.Step are no longer pulling the ‘stage’ prop directly from their parents. They are subscribing to it from context so the extra div in place is not blocking props being passed further down the tree. The App still works!

This now gives us a huge amount of flexibility. We can reuse our component to dynamically create complex variations of our Stepper component without worrying if our Application will break

Although we can use this component anywhere in our application, it’s still not truly reusable.We still need the boilerplate of context in order for it to work.

In the next part of this series I will discuss how we can use render props to achieve the same goals without having to rely on wiring up context to share state between components in our application.