Organizing Selectors

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

Organizing Selectors Overview

Organizing Selectors 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 organizing selectors 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 { 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.

Organizing Selectors Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to organizing selectors.

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 Organizing Selectors Works in Redux

Organizing Selectors 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 Organizing Selectors

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

Key Takeaways

Organizing Selectors is a core part of working effectively with Redux.
Start small and keep organizing selectors focused on a single goal.
Apply consistent patterns so organizing selectors scales across your project.
Practise and document organizing selectors to keep your workflow maintainable.

Pro Tip

Practise organizing selectors on a throwaway project first. It is far cheaper to learn Redux mistakes there than on important work.