Generated Actions

Generated Actions Overview

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

Good generated actions 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.

Generated Actions Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to generated actions.

How Generated Actions Works in Redux

Generated Actions 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 Generated Actions

In modern apps, generated actions 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

• Skipping edge cases and error handling when using generated actions.
• Not verifying the result of generated actions before moving on.
• Over-complicating generated actions before you actually need the extra flexibility.
• Ignoring documentation, which makes generated actions hard for the next person to follow.

Key Takeaways

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