Skip to content

Combining Reducers

In this lesson you will learn combining reducers in Redux, why it matters within reducers, and how to use it correctly with clear, copy-ready examples.

Combining Reducers Overview

At its core, combining reducers is about doing one thing well in Redux. Once you understand the pattern, you can apply it consistently across projects and teams.

Good combining reducers pays off across the whole project: fewer surprises, easier collaboration, and smoother onboarding. The snippet below is a solid starting point.

import { createSlice } from '@reduxjs/toolkit';

const counterSlice = createSlice({
  name: 'counter',
  initialState: { value: 0 },
  reducers: {
    increment: (state) => { state.value += 1; },
    addBy: (state, action) => { state.value += action.payload; },
  },
});

export const { increment, addBy } = counterSlice.actions;
export default counterSlice.reducer;

createSlice generates actions and a reducer together; Immer lets you write safe 'mutating' updates.

Combining Reducers Example

const slice = createSlice({ name, initialState, reducers });
const store = configureStore({ reducer: { key: slice.reducer } });
// dispatch(slice.actions.something())
  • Start from a minimal Combining Reducers example and grow it only as needed.
  • Keep things explicit so Combining Reducers behaves the same for everyone on the team.
  • Name things clearly so teammates understand your Combining Reducers at a glance.
  • Verify Combining Reducers works as expected before relying on it in important work.

Redux Cheatsheet

Quick Redux Toolkit reference related to combining reducers.

Concept Example Purpose
Store configureStore({ reducer }) Hold app state
Slice createSlice({ name, reducers }) State + actions together
Read state useSelector((s) => s.x) Get data in components
Dispatch useDispatch() Send actions
Async createAsyncThunk(...) Handle side effects
Data fetching createApi(...) RTK Query endpoints
Derived data createSelector(...) Memoized computations

How Combining Reducers Works in Redux

Combining Reducers 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.

createSlice generates actions and a reducer together; Immer lets you write safe 'mutating' updates.

  • 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 Combining Reducers

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

Concern Recommendation
Boilerplate Use Redux Toolkit (createSlice)
Server data Prefer RTK Query over manual thunks
Performance Memoize selectors with createSelector
Types Use typed useAppSelector/useAppDispatch hooks

Common Mistakes

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

Key Takeaways

  • Combining Reducers is a core part of working effectively with Redux.
  • Start small and keep combining reducers focused on a single goal.
  • Apply consistent patterns so combining reducers scales across your project.
  • Practise and document combining reducers to keep your workflow maintainable.

Pro Tip

Bookmark this combining reducers pattern and reuse it. Consistency across your Redux work is worth more than clever one-off solutions.