Unidirectional Data Flow

Unidirectional Data Flow Overview

Unidirectional Data Flow is something you will reach for often in Redux. It keeps your workflow predictable and makes your intent obvious to reviewers and teammates.

When you learn unidirectional data flow properly, you avoid the guesswork that leads to mistakes and rework. The example below shows the shape you will use in most real Redux projects.

import { configureStore } from '@reduxjs/toolkit';
import { Provider } from 'react-redux';

const store = configureStore({ reducer: rootReducer });

function App() {
  return (
    <Provider store={store}>
      <Root />
    </Provider>
  );
}

A Provider makes the single Redux store available to every component in the tree.

Unidirectional Data Flow Example

const slice = createSlice({ name, initialState, reducers });
const store = configureStore({ reducer: { key: slice.reducer } });
// dispatch(slice.actions.something())

• Start from a minimal Unidirectional Data Flow example and grow it only as needed.
• Keep things explicit so Unidirectional Data Flow behaves the same for everyone on the team.
• Name things clearly so teammates understand your Unidirectional Data Flow at a glance.
• Verify Unidirectional Data Flow works as expected before relying on it in important work.

Redux Cheatsheet

Quick Redux Toolkit reference related to unidirectional data flow.

How Unidirectional Data Flow Works in Redux

Unidirectional Data Flow follows Redux's predictable data flow: components dispatch actions, reducers compute the next state from the previous state and the action, and subscribed components re-render.

A Provider makes the single Redux store available to every component in the tree.

• State lives in a single, read-only store.
• Actions are the only way to describe a change.
• Reducers are pure functions that return the next state.
• Redux Toolkit removes most boilerplate with slices and thunks.

Practical Guidance for Unidirectional Data Flow

In modern apps, unidirectional data flow should use Redux Toolkit rather than hand-written Redux. Keep state minimal, colocate logic in slices, and use RTK Query for server data.

Common Mistakes

• Copying unidirectional data flow commands or snippets without understanding what each part does.
• Skipping edge cases and error handling when using unidirectional data flow.
• Not verifying the result of unidirectional data flow before moving on.
• Over-complicating unidirectional data flow before you actually need the extra flexibility.

Key Takeaways

• Unidirectional Data Flow is a core part of working effectively with Redux.
• Start small and keep unidirectional data flow focused on a single goal.
• Apply consistent patterns so unidirectional data flow scales across your project.
• Practise and document unidirectional data flow to keep your workflow maintainable.