createSlice

createSlice Overview

createSlice 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 createslice focused and predictable. Start from the minimal example here, then add only the complexity your situation actually needs.

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.

createSlice Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to createslice.

How createSlice Works in Redux

createSlice 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 createSlice

In modern apps, createslice 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 createslice.
• Not verifying the result of createslice before moving on.
• Over-complicating createslice before you actually need the extra flexibility.
• Ignoring documentation, which makes createslice hard for the next person to follow.

Key Takeaways

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