Derived State

Derived State Overview

Derived State lets you work with Redux in a way that stays clear, repeatable, and easy to scale. Instead of ad-hoc steps, you follow a pattern that other developers recognise immediately.

The key is to keep derived state focused and predictable. Start from the minimal example here, then add only the complexity your situation actually needs.

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

const selectItems = (state) => state.cart.items;

export const selectCartTotal = createSelector(
  [selectItems],
  (items) => items.reduce((sum, i) => sum + i.price * i.qty, 0),
);

createSelector memoizes derived data so it only recomputes when its inputs change.

Derived State Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to derived state.

How Derived State Works in Redux

Derived State 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.

createSelector memoizes derived data so it only recomputes when its inputs change.

• 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 Derived State

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

Key Takeaways

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