Questions
9 of 14
1What is a slice in Redux Toolkit?
2How is a slice different from a traditional Redux reducer?
3What are the key properties inside createSlice()?
4How does createSlice() automatically generate action creators?
5What does the name field in a slice represent?
6How do you combine multiple slices into one store?
7How do you access a slice’s state in a component using?
8Can you modify the state directly in a slice reducer? Why does it work?
9What’s the purpose of extraReducers in createSlice()?
10How do you handle async actions (e.g., thunks) inside a slice using extraReducers?
11What is the difference between reducers and extraReducers in a slice?
12How do you organize slices in a large application?
13Can multiple slices modify the same part of state?
14How do you reset a slice’s state to its initial value?
RTKRTK
Basics
Slice
Actions
Reducers
RTK Query
Store
Thunk
Scenario Based
09 / 14

What’s the purpose of extraReducers in createSlice()?

The extraReducers field in createSlice() lets a slice respond to actions that weren’t defined inside its own reducers. It’s commonly used to handle actions generated by async thunks or actions from other slices.

When to Use extraReducers
  1. 1

    To handle actions from createAsyncThunk() (like pending, fulfilled, and rejected).

  2. 2

    To respond to actions defined in other slices.

  3. 3

    To keep reducers modular while still reacting to shared global actions.

Example: Using extraReducers with createAsyncThunk