Give Your React Apps an Edge: Mastering Redux Toolkit

As React developers, we know that state management is a critical aspect of building complex applications. Redux has been a popular choice for managing state in large-scale React projects. However, setting up and maintaining a Redux store can become cumbersome, leading to boilerplate code and reduced developer productivity.

Redux Toolkit comes to the rescue, providing a streamlined and opinionated way to use Redux efficiently. It simplifies the setup process, reduces boilerplate, and offers advanced features for handling asynchronous operations, optimized performance, and more.

‍

Understanding React Redux Toolkit

Here, I will give an overview of the Redux Toolkit. Redux toolkit, previously known as Redux Starter kit, is the official, opinionated, batteries-included toolset for efficient Redux development. This excellent tool is part of the core Redux toolkit package, which is designed to simplify common Redux use cases. The motto of Redux toolkit is to provide good defaults to reduce the boilerplate code and complexity in managing the global state of your React app.

Stop for a moment and think of the toolkit as a Redux store, carrying all convenient packaging for your Redux development. The main redux toolkit packages are @reduxjs/toolkit and react-redux. Importantly, Redux toolkit automatically generates actions and reducers, reducing the need to write boilerplate code. And let me tell you something else, Redux Toolkit includes Redux Thunk for async logic. Isn't it exciting?

Enough of the talk, let's see how you can use the redux toolkit in your react app:

Copy
     import { configureStore } from '@reduxjs/toolkit';
    import rootReducer from './reducer';
    
    const store = configureStore({
      reducer: rootReducer
    });
    
    export default store;
     

In the code snippet above, I have imported the configureStore method from the core Redux toolkit package. This function sets up the redux store with the root reducer and some default middleware from the Redux toolkit.

‍

Advanced Redux Toolkit Concepts

Don't worry, now, we're getting into the real Redux logic. To write Redux logic more effectively, Redux Toolkit offers some powerful abstractions such as createAsyncThunk, createSlice, and createEntityAdapter.

‍

Redux Toolkit's 'createAsyncThunk' for Asynchronous Operations

createAsyncThunk is part of the Redux Toolkit package, and let me tell you, it's a game-changer! It simplifies managing async operations where you need to dispatch an action before data fetching, upon successful data retrieval, or when encountering errors.

Here's a quick look at how we can use createAsyncThunk in our Redux Toolkit application:

In this code snippet, fetchData is the action creator function that uses the createAsyncThunk method. It automatically generates three action types (request, success, failure) saving us from writing extra boilerplate code.

‍

Customizing Redux State with createSlice

Redux Toolkit's createSlice automatically generates reducer functions and corresponding action creators based on the reducers and name options provided.

If we integrate createSlice and createAsyncThunk in the same reducer function, integration looks something like this:

Here, we've defined a slice of Redux store function for data fetching. With the actions generated by createAsyncThunk, we've defined different states based on action outcomes.

‍

Advanced Redux State Setup with createEntityAdapter

This code block shows how the createEntityAdapter comes in handy to manage normalized data in the Redux store.

‍

Optimizing Performance with Immer

Immer is a JavaScript package that simplifies the process of writing immutable update logic in your Redux reducers. The beauty of Immer is that it enables you to write code that looks like mutable logic, while actually applying immutable updates under the hood.

Integrating Immer allows us to focus on writing simpler and more readable reducer functions without worrying about accidentally muting the state. Redux Toolkit leverages the advantages of Immer as it's used under the hood in createSlice and createReducer.

Here's a glance at a reducer function in a React redux toolkit with Immer:

Notice the nice and clean reducer function. Within addTodo, the push operation is made directly on the state without returning a new state array, thanks to Immer. Similarly, toggleTodo is directly updating the needed todo object's completed property without any mutations.

When we use the redux toolkit core methods such as createSlice, behind the scenes, it uses the infrastructure provided by Immer for the Redux store and state updates.

‍

Fine-tuning State Management

React Redux toolkit was designed with the larger goal of simplifying the redux logic, data fetching and eliminating large quantities of boilerplate code from a developer's life.

‍

Middleware Integration with Redux Toolkit

One of the powerful features provided by the Redux toolkit package is support for middleware integration which is utilized by Redux applications extensively. Middleware lets you add extra control or processing to your Redux flow. The Redux toolkit core package leverages redux-thunk for async middleware support, but we can certainly add support for other middleware such as redux-saga.

That isn't all, though. It also provides configurable middleware for additional logic out-of-box. To expand on this, here's how you could customize your middleware:

In this example, the redux-logger middleware is concatenated to the list of default middleware provided by @reduxjs/toolkit.

‍

Creating Custom Middleware

Redux toolkit does an excellent job assisting us with its capabilities in creating custom Redux middleware as well.

Here's an example of how Redux Toolkit simplifies the process:

You can apply this custom middleware by following the getDefaultMiddleware() concatenation pattern I showed you earlier.

‍

Combining Redux Toolkit with React

Let's now integrate our Redux Toolkit with React in our feature-packed journey. Using Redux with react-redux's integration is a norm with modern apps that manages a vast and intricate global store.

‍

React-Redux Integration with Redux Toolkit

You might already know about react-redux Provider and connect. Before Redux Toolkit, we used to integrate our Redux store function with the provider component by wrapping the React app in the Provider component. We are using here @reduxjs/toolkit in place of classic redux and react-redux packages.

Now every react-redux component underneath Provider in the component tree can access the Redux store.

‍

Selector Functions for Efficient Data Retrieval

Selectors are functions that know how to extract specific pieces of information from your Redux store. They are a vital aspect of state management within React-Redux applications, helping to keep your state structure as minimal as possible.

In the Redux Toolkit, when we define a createSlice, it automatically generates selectors. You can see that in action here:

The useSelector hook in the react-redux library is used to extract data from the Redux store state by calling our state.user.value slice. We can avoid the bother to write switch statements, and this is where Redux Toolkit is a favorite!

‍

Testing Redux Toolkit Applications

Testing is love for we developers! Especially when it comes to the React and Redux toolkit. Redux toolkit makes testing your components, actions, and reducers a lot easier with the tools provided in its arsenal.

‍

Writing Unit Tests for Redux Toolkit Slices

Most of the time, you would want to write unit tests for the most meaningful parts of your app. For Redux Toolkit applications, as createSlice() generates both reducers and actions, it's advisable to write tests that cover these two aspects. Check out how you can do that below:

In the above unit test, I am testing the todos slice functions that were automatically created using createSlice().

‍

Integrating Persistence with Redux Toolkit

So, you've been working with React and Redux Toolkit and thought about how to persist your Redux store? Like you, many developers want their applications to maintain their state even after the page is refreshed. Thanks to Redux Toolkit, persisting state to local storage has never been easier!

‍

Persisting State in Local Storage

The simplest way to persist the state is to use the local storage API of the browser where the redux state is stringified to be stored and parsed when retrieved.

Here is how you tackle it with Redux Toolkit:

The subscribe function is used to listen for state changes, writing the state to the localStorage API whenever a state change occurs.

And voila - our Redux Toolkit state is now persisting, even on refreshing pages. Though, we should know that this approach can be further optimized as manual synchronization can be problematic in advanced use cases.

‍

Advanced DevTools Configuration

As a developer, you're already aware of how invaluable DevTools can be for debugging our applications. The same stands true for Redux development. The Redux DevTools extension provides us with some powerful features like action history, state diff, and even hot reloading.

‍

Improving Development Experience with Redux DevTools

Your journey towards efficient Redux development wouldn't be complete without the Redux DevTools. Redux Toolkit provides out-of-the-box support for the Redux DevTools browser extension.

A simple configuration can save us from writing tedious lines of code to implement redux-devtools:

In our Redux store configuration, the devTools option is set to true automatically if NODE_ENV is not 'production'.

The time travel feature of the Redux DevTools extension is incredibly powerful - it lets us step forwards and backwards through the history of state changes, and even lets us modify it! If the current state of your app isn't optimal, the official opinionated batteries included toolset for efficient redux development provides you with the tools to easily review and modify previous states.

‍

Redux Toolkit Best Practices

Let's seal the deal with some best practices! Employ these techniques in your react and redux toolkit adventures and you'll find your redux development experience streamlined.

‍

Scalable Folder Structure for Large Applications

One common challenge developers face is managing a scalable and robust folder structure for large applications. Your Redux Toolkit should include a scalable folder structure that separates concerns into different folders:

• Features: This folder contains subfolders for each feature of your application. Each subfolder includes slices, selectors, actions, and tests.
• App: This folder contains the root reducer and store configuration.
• Shared: This folder contains reusable components, hooks, utils, and constants.
• API: This folder includes API interface layer - the setup files for your API endpoints.

‍

Separation of Concerns: Selectors, Reducers, and Actions

In Redux, actions, reducers, and selectors have unique roles. Keep them focused on their respective roles:

• Selectors: Should only extract and compute derived data.
• Actions: Should only describe “what happened”, and provide the minimal necessary information.
• Reducers: This will dictate how the state is updated based on actions.

Try to make a habit of using Redux Toolkit's createSlice and createAsyncThunk. This will not only generate action creators and reducers automatically but will keep them close to each other. As your app grows, so do the convenience and effectiveness of these practices.

‍

Conclusion

We have navigated through the vast sea of React Redux Toolkit in this blog post, starting from understanding the basic concepts to more advanced features like asynchronous operations, middleware, and custom hooks. The Redux Toolkit targets to make Redux fun again by reducing the boilerplate code and bringing more simplicity to implement complex state management problems.

The concept we discussed throughout the course can be a game-changer in how developers deal with Redux in their applications. Just like the Redux Toolkit, there are unique tools developed to simplify our development process, one such tool being WiseGPT by DhiWise .

Just as Redux Toolkit has contributed to making state management more efficient, WiseGPT makes it easier for developers to integrate APIs into their React projects. It's an AI-powered plugin that learns and mirrors your coding style for auto-creating models and functions.

We've sailed across many Redux Toolkit concepts, realized its potential in efficient Redux development, and explored how it significantly reduces the need for boilerplate code. Redux Toolkit, as an official opinionated batteries-included toolset for Redux, has truly made Redux accessible, fun, and enjoyable.

So next time you hear anyone boasting too much boilerplate code in Redux, give them a friendly nod and let them in on the fascinating world of Redux Toolkit.

Looking forward to our next journey together - until then, stay curious, stay coding!

     import { createAsyncThunk } from '@reduxjs/toolkit';
    import api from 'path/to/api';
    
    export const fetchData = createAsyncThunk(
      'points/fetch',
      async () => {
        const response = await api.get('/points');
        return response.data;
      }
    );
     

     import { createSlice } from '@reduxjs/toolkit';
    import { fetchData } from './actions';
    
    const dataSlice = createSlice({
      name: 'data',
      initialState: { entities: [], loading: 'idle' },
      reducers: {},
      extraReducers: (builder) => {
        builder
          .addCase(fetchData.pending, (state) => {
            state.loading = 'loading';
          })
          .addCase(fetchData.fulfilled, (state, action) => {
            state.loading = 'idle';
            state.entities = action.payload;
          });
      },
    });
    
    export default dataSlice.reducer;
     

     const adapterTemplate = createEntityAdapter({
      selectId: template => template.id,
      sortComparer: (a, b) => a.title.localeCompare(b.title)
    })
     

     const todosSlice = createSlice({
      name: 'todos',
      initialState: [],
      reducers: {
        addTodo: (state, action) => {
          state.push({text: action.payload, completed: false})
        },
        toggleTodo: (state, action) => {
          const todo = state[action.payload]
          todo.completed = !todo.completed
        }
      }
    })
     

     import { configureStore } from '@reduxjs/toolkit';
    import logger from 'redux-logger';
    import rootReducer from './rootReducer';
    
    const store = configureStore({
      reducer: rootReducer,
      middleware: (getDefaultMiddleware) => getDefaultMiddleware().concat(logger)
    });
    
    export default store;
     

     export const actionLogger = storeAPI => next => action => {
      console.log('dispatching', action.type)
      let result = next(action)
      console.log('state after dispatch', storeAPI.getState())
      return result
    }
     

     import { Provider } from 'react-redux';
    import store from './app/store';
    import App from './App';
    
    const RootApp = () => (
      <Provider store={store}>
        <App />
      </Provider>
    );
    
    export default RootApp;
    
     

     import { useSelector } from 'react-redux';
    
    
    function CurrentUser() {
      const user = useSelector(state => state.user.value);
    
      return (
        <div>
          Current User: {user}
        </div>
      )
    }
     

     import todos, { addTodo, toggleTodo } from './todosSlice'
    
    describe('todos reducer', () => {
      const initialState = []
      it('should handle initial state', () => {
        expect(todos(undefined, { type: 'unknown' })).toEqual([])
      })
    
      it('should handle addTodo', () => {
        const actual = todos(initialState, addTodo('Run the tests'))
        expect(actual.length).toBe(1)
      })
    
      it('should handle toggleTodo', () => {
        const actual = todos([ {text: 'Run the tests', completed: false} ], toggleTodo(0))
        expect(actual[0].completed).toBe(true)
      })
    })
     

     import { configureStore } from '@reduxjs/toolkit';
    import rootReducer from './rootReducer';
    
    const persistedState = localStorage.getItem('reduxState')
                           ? JSON.parse(localStorage.getItem('reduxState'))
                           : {}
    
    const store = configureStore({
      reducer: rootReducer,
      preloadedState: persistedState
    });
    
    store.subscribe(()=>{
      localStorage.setItem('reduxState', JSON.stringify(store.getState()))
    })
    
    export default store;
     

     import { configureStore } from '@reduxjs/toolkit';
    import rootReducer from './rootReducer';
    
    const store = configureStore({
      reducer: rootReducer,
      devTools: process.env.NODE_ENV !== 'production',
    });
    
    export default store;