Reducer Rules

Reducer Rules Overview

Reducer Rules 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 reducer rules 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 { 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.

Reducer Rules Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to reducer rules.

How Reducer Rules Works in Redux

Reducer Rules 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 Reducer Rules

In modern apps, reducer rules 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 reducer rules commands or snippets without understanding what each part does.
• Skipping edge cases and error handling when using reducer rules.
• Not verifying the result of reducer rules before moving on.
• Over-complicating reducer rules before you actually need the extra flexibility.

Key Takeaways

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