In the previous section we described a solution that mixes state and render. This works, but is generally a bad idea because it makes it more difficult to reuse view-specific code.

Your React components should be split up into two types: those that manage state (stateful components) and those that just deal with the display of data (pure components), also called smart/dumb components.

The goal is to design stateless components that accept properties and are only responsible for rendering into a view. This makes it easier to test and reuse those components.

A pure LocationsComponent component would look like this (using functional components):

function LocationsComponent({ locations }) {
  return (
      {, index) => {
          return <li key={index}>{}</li>

This component is simpler because it does not depend on state changes. In this case, state must be managed by a wrapping container component. AltContainer is a component you can use to declaratively connect a Store to the pure components.

import locationStore from '../stores/LocationStore';

function LocationsWrapper() {
  return (
    <AltContainer store={ locationStore }>
      <LocationsComponent />

AltContainer will automatically listen and unlisten to changes in your Store. When a change happens, AltContainer will trigger a re-render of the children components, passing the new state as properties. In the case of multiple stores, the states will be merged befre passing them as properties.

With this design the wrapped component can now be re-used in other places, since it’s not tied to a particular Store. All it will do is accept a list of locations and render them. AltContainer handles the listening and unlistening of your Stores.