|
| 1 | +--- |
| 2 | +id: lesson-2 |
| 3 | +title: "Advanced State Management with Redux Toolkit" |
| 4 | +sidebar_label: Lesson - 2 |
| 5 | +sidebar_position: 2 |
| 6 | +description: "In this lesson, you will learn advanced state management techniques using Redux Toolkit, including handling asynchronous actions with createAsyncThunk and managing complex state logic." |
| 7 | +tags: |
| 8 | + [ |
| 9 | + courses, |
| 10 | + redux-toolkit, |
| 11 | + react-js, |
| 12 | + state-management, |
| 13 | + redux, |
| 14 | + advanced, |
| 15 | + ] |
| 16 | +--- |
| 17 | + |
| 18 | +## Introduction |
| 19 | + |
| 20 | +Creating an API utility for your application is an essential step to manage and separate concerns effectively. By centralizing your API calls, you simplify the process of managing data retrieval, error handling, and side effects, resulting in cleaner and more maintainable code. This lesson will guide you through creating an API utility and using it with Redux Toolkit to manage state in a structured and efficient way. |
| 21 | + |
| 22 | +## Steps to Create an API Utility |
| 23 | + |
| 24 | +### 1. Creating an API Utility |
| 25 | + |
| 26 | +You'll often want to separate your API calls into a dedicated utility file. This approach allows you to centralize the logic for making HTTP requests, making your code more modular and easier to maintain. |
| 27 | + |
| 28 | +```javascript title = "src/features/posts/postsAPI.js" |
| 29 | +import axios from 'axios'; |
| 30 | + |
| 31 | +export const fetchPosts = () => { |
| 32 | + return axios.get('https://jsonplaceholder.typicode.com/posts'); |
| 33 | +}; |
| 34 | +``` |
| 35 | + |
| 36 | +*Description:* The above code creates an API utility using Axios to fetch posts from a placeholder API. This utility function can be reused across different parts of your application wherever you need to fetch posts data. |
| 37 | + |
| 38 | +### 2. Using Thunks in a Component |
| 39 | + |
| 40 | +With the API utility created, you can now use it in your Redux slices to handle asynchronous actions. Redux Toolkit provides `createAsyncThunk` to simplify this process. |
| 41 | + |
| 42 | +```javascript title = "src/features/posts/Posts.js" |
| 43 | +import React, { useEffect } from 'react'; |
| 44 | +import { useSelector, useDispatch } from 'react-redux'; |
| 45 | +import { fetchPostsAsync } from './postsSlice'; |
| 46 | + |
| 47 | +function Posts() { |
| 48 | + const dispatch = useDispatch(); |
| 49 | + const posts = useSelector((state) => state.posts.items); |
| 50 | + const status = useSelector((state) => state.posts.status); |
| 51 | + const error = useSelector((state) => state.posts.error); |
| 52 | + |
| 53 | + useEffect(() => { |
| 54 | + if (status === 'idle') { |
| 55 | + dispatch(fetchPostsAsync()); |
| 56 | + } |
| 57 | + }, [status, dispatch]); |
| 58 | + |
| 59 | + return ( |
| 60 | + <div> |
| 61 | + {status === 'loading' && <div>Loading...</div>} |
| 62 | + {status === 'succeeded' && ( |
| 63 | + <ul> |
| 64 | + {posts.map((post) => ( |
| 65 | + <li key={post.id}>{post.title}</li> |
| 66 | + ))} |
| 67 | + </ul> |
| 68 | + )} |
| 69 | + {status === 'failed' && <div>{error}</div>} |
| 70 | + </div> |
| 71 | + ); |
| 72 | +} |
| 73 | + |
| 74 | +export default Posts; |
| 75 | +``` |
| 76 | + |
| 77 | +*Description:* This component uses the `fetchPostsAsync` thunk to fetch posts data when the component mounts. It leverages the Redux state to manage loading, success, and error states, providing a responsive user experience. |
| 78 | + |
| 79 | + |
| 80 | + |
| 81 | +*Description:* The image above provides a visual representation of how Redux Toolkit thunks can be used to manage asynchronous operations in your Redux state management. |
| 82 | + |
| 83 | +## Managing Complex State Logic |
| 84 | + |
| 85 | +For complex applications, it's important to structure your state effectively to avoid deeply nested structures. Normalizing state makes it easier to update and manage, reducing the likelihood of bugs and improving performance. |
| 86 | + |
| 87 | +### 1. Normalizing State Structure |
| 88 | + |
| 89 | +```javascript title = "src/features/entities/entitiesSlice.js" |
| 90 | +import { createSlice } from '@reduxjs/toolkit'; |
| 91 | + |
| 92 | +const entitiesSlice = createSlice({ |
| 93 | + name: 'entities', |
| 94 | + initialState: { |
| 95 | + users: {}, |
| 96 | + posts: {}, |
| 97 | + comments: {}, |
| 98 | + }, |
| 99 | + reducers: { |
| 100 | + addUser: (state, action) => { |
| 101 | + const user = action.payload; |
| 102 | + state.users[user.id] = user; |
| 103 | + }, |
| 104 | + addPost: (state, action) => { |
| 105 | + const post = action.payload; |
| 106 | + state.posts[post.id] = post; |
| 107 | + }, |
| 108 | + addComment: (state, action) => { |
| 109 | + const comment = action.payload; |
| 110 | + state.comments[comment.id] = comment; |
| 111 | + }, |
| 112 | + }, |
| 113 | +}); |
| 114 | + |
| 115 | +export const { addUser, addPost, addComment } = entitiesSlice.actions; |
| 116 | +export default entitiesSlice.reducer; |
| 117 | +``` |
| 118 | + |
| 119 | +*Description:* This slice normalizes the state structure by storing users, posts, and comments in separate dictionaries indexed by their IDs. This approach allows for efficient state updates and access. |
| 120 | + |
| 121 | +### 2. Using Entity Adapter |
| 122 | + |
| 123 | +Redux Toolkit provides `createEntityAdapter` to manage normalized state more efficiently. It includes helpers for common operations like adding, updating, and removing entities. |
| 124 | + |
| 125 | +```javascript title="src/features/posts/postsSlice.js" |
| 126 | +import { createSlice, createEntityAdapter } from '@reduxjs/toolkit'; |
| 127 | +import { fetchPosts } from './postsAPI'; |
| 128 | + |
| 129 | +const postsAdapter = createEntityAdapter(); |
| 130 | + |
| 131 | +const postsSlice = createSlice({ |
| 132 | + name: 'posts', |
| 133 | + initialState: postsAdapter.getInitialState({ |
| 134 | + status: 'idle', |
| 135 | + error: null, |
| 136 | + }), |
| 137 | + reducers: {}, |
| 138 | + extraReducers: (builder) => { |
| 139 | + builder |
| 140 | + .addCase(fetchPosts.pending, (state) => { |
| 141 | + state.status = 'loading'; |
| 142 | + }) |
| 143 | + .addCase(fetchPosts.fulfilled, (state, action) => { |
| 144 | + state.status = 'succeeded'; |
| 145 | + postsAdapter.setAll(state, action.payload); |
| 146 | + }) |
| 147 | + .addCase(fetchPosts.rejected, (state, action) => { |
| 148 | + state.status = 'failed'; |
| 149 | + state.error = action.error.message; |
| 150 | + }); |
| 151 | + }, |
| 152 | +}); |
| 153 | + |
| 154 | +export const { selectAll: selectAllPosts } = postsAdapter.getSelectors( |
| 155 | + (state) => state.posts |
| 156 | +); |
| 157 | + |
| 158 | +export default postsSlice.reducer; |
| 159 | +``` |
| 160 | + |
| 161 | +*Description:* The `postsAdapter` provides a set of pre-built reducers and selectors to manage the posts state. This approach simplifies the implementation of common CRUD operations and ensures consistent state structure. |
| 162 | + |
| 163 | +## Conclusion |
| 164 | + |
| 165 | +In this lesson, you learned how to create an API utility and integrate it with Redux Toolkit to manage asynchronous actions. You also explored advanced state management techniques, including normalizing state structures and using entity adapters for efficient state updates. By following these practices, you can build more robust and maintainable Redux applications. |
| 166 | + |
| 167 | +--- |
| 168 | + |
| 169 | +This approach to advanced state management with Redux Toolkit ensures your application remains scalable and maintainable as it grows in complexity. |
0 commit comments