Thunk Functions

Thunk Functions Overview

Thunk Functions 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 thunk functions 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 { createAsyncThunk, createSlice } from '@reduxjs/toolkit';

export const fetchUser = createAsyncThunk('user/fetch', async (id) => {
  const res = await fetch(`/api/users/${id}`);
  return res.json();
});

const userSlice = createSlice({
  name: 'user',
  initialState: { data: null, status: 'idle' },
  reducers: {},
  extraReducers: (builder) => {
    builder
      .addCase(fetchUser.pending, (s) => { s.status = 'loading'; })
      .addCase(fetchUser.fulfilled, (s, a) => { s.status = 'idle'; s.data = a.payload; });
  },
});

createAsyncThunk handles async flows and dispatches pending/fulfilled/rejected actions automatically.

Thunk Functions Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to thunk functions.

How Thunk Functions Works in Redux

Thunk Functions 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.

createAsyncThunk handles async flows and dispatches pending/fulfilled/rejected actions automatically.

• 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 Thunk Functions

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

Key Takeaways

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