Mock API Requests

Mock API Requests Overview

Mock API Requests 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 mock api requests focused and predictable. Start from the minimal example here, then add only the complexity your situation actually needs.

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.

Mock API Requests Example

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

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

Redux Cheatsheet

Quick Redux Toolkit reference related to mock api requests.

How Mock API Requests Works in Redux

Mock API Requests 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 Mock API Requests

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

Key Takeaways

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