Questions

11 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?

RTK

11 / 14

What is the difference between reducers and extraReducers in a slice?

In Redux Toolkit, both reducers and extraReducers define how the slice state changes in response to actions, but they are used in different contexts.

Key Differences

1
reducers handle actions defined within the same slice. These actions are automatically generated by Redux Toolkit.
2
extraReducers handle actions from outside the slice, such as async thunks or actions from other slices.
3
reducers use a simple object syntax, while extraReducers often use a builder callback for better type safety and flexibility.

Example: reducers vs extraReducers