Redux Toolkit setup in React Native

Introduction

Redux Toolkit helps you manage app data in one place easily. It makes your app organized and predictable.

You want to share data between many screens in your app.

You need to keep track of user actions and app state clearly.

Your app has complex data that changes often.

You want to avoid bugs caused by scattered data updates.

You want a simple way to write Redux code without too much setup.

Syntax

React Native

import { configureStore } from '@reduxjs/toolkit';
import sliceReducer from './sliceFile';

const store = configureStore({
  reducer: {
    sliceName: sliceReducer
  }
});

export default store;

configureStore sets up the Redux store with good defaults.

You add your data logic in sliceReducer which comes from a slice file.

Examples

This example creates a store with a counter slice to manage a number.

React Native

import { configureStore } from '@reduxjs/toolkit';
import counterReducer from './counterSlice';

const store = configureStore({
  reducer: {
    counter: counterReducer
  }
});

export default store;

This example sets up a store with a user slice to manage user info.

React Native

import { configureStore } from '@reduxjs/toolkit';
import userReducer from './userSlice';

const store = configureStore({
  reducer: {
    user: userReducer
  }
});

export default store;

Sample App

This app shows a number that you can increase or decrease by pressing buttons. It uses Redux Toolkit to keep the number in a central store.

React Native

import React from 'react';
import { Provider, useSelector, useDispatch } from 'react-redux';
import { configureStore, createSlice } from '@reduxjs/toolkit';
import { Text, View, Button } from 'react-native';

const counterSlice = createSlice({
  name: 'counter',
  initialState: { value: 0 },
  reducers: {
    increment: state => { state.value += 1; },
    decrement: state => { state.value -= 1; }
  }
});

const store = configureStore({
  reducer: {
    counter: counterSlice.reducer
  }
});

function Counter() {
  const count = useSelector(state => state.counter.value);
  const dispatch = useDispatch();

  return (
    <View style={{ padding: 20, alignItems: 'center' }}>
      <Text style={{ fontSize: 24, marginBottom: 10 }}>Count: {count}</Text>
      <Button title="Increase" onPress={() => dispatch(counterSlice.actions.increment())} />
      <View style={{ height: 10 }} />
      <Button title="Decrease" onPress={() => dispatch(counterSlice.actions.decrement())} />
    </View>
  );
}

export default function App() {
  return (
    <Provider store={store}>
      <Counter />
    </Provider>
  );
}

Important Notes

Always wrap your app in <Provider> to give access to the store.

Use createSlice to write reducers and actions together simply.

Redux Toolkit includes good defaults like Redux DevTools support automatically.

Summary

Redux Toolkit simplifies setting up Redux store and reducers.

Use configureStore to create the store with slices.

Wrap your app in <Provider> to connect Redux.

Practice

1. What is the main purpose of configureStore in Redux Toolkit?

easy

A. To create the Redux store with reducers and middleware setup automatically

B. To dispatch actions to update the store

C. To connect React components to the Redux store

D. To define action creators manually

Solution

1. Step 1: Understand configureStore role

   configureStore is a Redux Toolkit function that simplifies creating the Redux store by automatically combining reducers and adding middleware.

2. Step 2: Differentiate from other Redux tasks

   Dispatching actions and connecting components are done elsewhere, not by configureStore.

3. Final Answer:

   To create the Redux store with reducers and middleware setup automatically -> Option A

4. Quick Check:

   configureStore creates store [OK]

Hint: Remember: configureStore builds the store, not dispatch or connect [OK]

Common Mistakes:

• Confusing store creation with dispatching actions
• Thinking configureStore connects React components
• Assuming manual action creators are needed here

2. Which of the following is the correct syntax to create a Redux store using Redux Toolkit?

easy

A. const store = createStore(rootReducer);

B. const store = configureStore(rootReducer);

C. const store = configureStore({ reducer: rootReducer });

D. const store = new Store(rootReducer);

Solution

1. Step 1: Recall Redux Toolkit store creation syntax

   Redux Toolkit uses configureStore with an object argument containing the reducer key.

2. Step 2: Identify correct usage

   const store = configureStore({ reducer: rootReducer }); correctly passes an object with reducer: rootReducer. Options A and C use old or invalid syntax. const store = configureStore(rootReducer); passes reducer directly without an object, which is incorrect.

3. Final Answer:

   const store = configureStore({ reducer: rootReducer }); -> Option C

4. Quick Check:

   configureStore expects an object with reducer [OK]

Hint: Use configureStore({ reducer: ... }) syntax exactly [OK]

Common Mistakes:

• Passing reducer directly instead of inside an object
• Using createStore instead of configureStore
• Trying to instantiate Store with new keyword

3. Given this Redux Toolkit slice setup, what will be the initial state of the store?

import { configureStore, createSlice } from '@reduxjs/toolkit';

const counterSlice = createSlice({
  name: 'counter',
  initialState: { value: 10 },
  reducers: {
    increment: state => { state.value += 1; }
  }
});

const store = configureStore({ reducer: { counter: counterSlice.reducer } });

console.log(store.getState());

medium

A. { counter: { value: 0 } }

B. {}

C. { value: 10 }

D. { counter: { value: 10 } }

Solution

1. Step 1: Identify initialState in slice

   The slice defines initialState: { value: 10 } for the counter.

2. Step 2: Understand store state shape

   The store combines reducers under the key counter, so the state shape is { counter: { value: 10 } }.

3. Final Answer:

   { counter: { value: 10 } } -> Option D

4. Quick Check:

   Initial state matches slice's initialState under reducer key [OK]

Hint: Initial state is inside reducer key in store state [OK]

Common Mistakes:

• Ignoring reducer key nesting in state
• Assuming initial value is 0 by default
• Confusing slice state with root state shape

4. Identify the error in this Redux Toolkit store setup code:

import { configureStore } from '@reduxjs/toolkit';

const store = configureStore(reducer: rootReducer);

export default store;

medium

A. Missing curly braces around the reducer argument object

B. Using configureStore instead of createStore

C. rootReducer should be a string, not a variable

D. Export statement is incorrect

Solution

1. Step 1: Check configureStore argument syntax

   configureStore expects an object argument, so the reducer must be inside curly braces: { reducer: rootReducer }.

2. Step 2: Verify other parts

   Using configureStore is correct. rootReducer is a variable, which is valid. Export statement is fine.

3. Final Answer:

   Missing curly braces around the reducer argument object -> Option A

4. Quick Check:

   configureStore({ reducer: ... }) needs braces [OK]

Hint: Always pass an object with reducer key to configureStore [OK]

Common Mistakes:

• Passing reducer directly without braces
• Confusing configureStore with createStore
• Thinking export default is wrong here

5. You want to connect your React Native app to Redux using Redux Toolkit. Which is the correct way to wrap your app component to provide the store? A) <Provider store={store}><App /></Provider> B) <StoreProvider store={store}><App /></StoreProvider> C) <ReduxProvider store={store}><App /></ReduxProvider> D) <App store={store} />

hard

A.

B.

C.

D.

Solution

1. Step 1: Identify the correct provider component

   Redux Toolkit uses the Provider component from react-redux to supply the store to the app.

2. Step 2: Confirm correct usage

   The Provider wraps the root App component with the store prop. Other options use incorrect or nonexistent components.

3. Final Answer:

   <Provider store={store}><App /></Provider> -> Option B

4. Quick Check:

   Use Provider from react-redux to connect store [OK]

Hint: Wrap app in for Redux connection [OK]

Common Mistakes:

• Using wrong provider component names
• Passing store as a prop directly to App
• Forgetting to wrap the app at all