Input Selectors

Input Selectors Overview

Input Selectors 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 input selectors 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.

Input Selectors Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to input selectors.

How Input Selectors Works in Redux

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

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

Key Takeaways

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