Introduction to Redux

Introduction to Redux

0%

1. Getting Started

In this section we will learn what Redux is, why it is useful, and most importantly when it is useful. We will also learn how to set up a basic react-redux application.

When to use Redux?

Setting up a React-Redux Application

2. Fundamental Concepts

In this section we will go through the fundamental concepts of Redux that are necessary to understand the workings of a Redux application. We will use code examples to understand the concepts and in the following section we will use them practically.

Store Dispatch Method

Redux Data Flow

3. Redux in Practice

In the previous section we looked at the basic concepts. In this section we use those basic concepts to understand some more complicated concepts and the structure of a Redux application. In the end we will also look at the Counter application to put together all the pieces of our knowledge together.

Redux Application Structure

Modifying the Template for Use

Creating the Redux Store

Creating a Slice

Understanding Slice

Using Selectors to access State

Modifying State by Dispatching Actions

Thunk Functions

Rules for Reducers

Understanding the Counter Application

4. Creating a React-Redux Application

This chapter is focused on practice hence we will utilize the knowledge we acquired in previous sections to create a practical application using Redux along with React.

The Application

Setting Up the Application

Creating the UI Skeleton

Creating the Profile Slice

Creating the Posts Slice

Completing the Posts feature

Displaying Number of Posts and Users

Adding CSS Styling

Course Content

Introduction to Redux

Rules for Reducers

There are certain rules while using Redux Reducers which we need to follow to avoid certain bugs or surprises.

Reducers should use only the state and action arguments to calculate the new state. They shouldn't access any external values;
Reducers must not perform asynchronous logic or side effects such as making API calls or running timers etc.;
The state should not be directly modified inside the reducer functions, instead, the reducer function should return a duplicate state object with updated values. This rule only applies when creating reducers manually. If we use createSlice to create a slice, we can modify the state directly.

It is important to note that in the case of createSlice reducers, we directly modify the state object, however, in the backend, Redux creates a new duplicate object and assigns it the new changes, so the rule is being followed, but in the backend.

Everything was clear?

Thanks for your feedback!

Section 3. Chapter 10

some-alt