Gain insights into Redux, an open-source library for managing app state. Learn about Redux store creation, middleware, state management, error handling, testing, and building robust applications.

react.tar.gz

jest

simplee

no server

Redux

In this course, you will take a deep dive into Redux, an open-source JavaScript library for managing application state.

You will start by running through what Redux is, general concepts, and basic implementation. With the basics out of the way, you will begin working on building a recipe book application, adding more bells and whistles to it as the course progresses. You will learn to create a Redux store, how to work with middleware, state management, error handling, testing, and a whole lot more.

By the end, you will have advanced knowledge of one the most popular libraries among React and Angular developers. You will have the skills to create highly performant and consistent.

The Ultimate Guide to Redux

## How does redux-thunk work?

The library is a small middleware that checks the `type` of every action dispatched. When it notices the action is actually a `function`, `redux-thunk` will call it, passing it the `dispatch()` and `getState()` functions as parameters and sending the return value to the reducers.


## Server communication

We can use the `redux-thunk` method to allow simple server communication by replacing the `setTimeout()` call from the previous example with a network call to the server:


~~~~~~~
import * as constants from 'constants/actionTypes';
import axios from 'axios';

const getRecipes = (limit = 100) => (dispatch) => {
  dispatch({ type: constants.FETCH_RECIPES_START, limit });

  axios.get(`recipes?limit=${ limit }`)
    .then(({ data }) => dispatch({type: constants.FETCH_RECIPES_DONE, data}))
    .catch(error => dispatch({type: constants.FETCH_RECIPES_ERROR, error}));
};

export getRecipes;
~~~~~~~

While this code might work for a very simple project, it will require a boilerplate for each API call we make. We discuss a more generic and cleaner approach to server communication in the Server Communication module.

# How does redux-thunk work?

The library is a small middleware that checks the `type` of every action dispatched. When it notices the action is actually a `function`, `redux-thunk` will call it, passing it the `dispatch()` and `getState()` functions as parameters and sending the return value to the reducers.


# Server communication

We can use the `redux-thunk` method to allow simple server communication by replacing the `setTimeout()` call from the previous example with a network call to the server:


~~~~~~~
import * as constants from 'constants/actionTypes';
import axios from 'axios';

const getRecipes = (limit = 100) => (dispatch) => {
  dispatch({ type: constants.FETCH_RECIPES_START, limit });

  axios.get(`recipes?limit=${ limit }`)
    .then(({ data }) => dispatch({type: constants.FETCH_RECIPES_DONE, data}))
    .catch(error => dispatch({type: constants.FETCH_RECIPES_ERROR, error}));
};

export getRecipes;
~~~~~~~

While this code might work for a very simple project, it will require a boilerplate for each API call we make. We discuss a more generic and cleaner approach to server communication in the Server Communication module.

# How does redux-thunk work?

The library is a small middleware that checks the `type` of every action dispatched. When it notices the action is actually a `function`, `redux-thunk` will call it, passing it the `dispatch()` and `getState()` functions as parameters and sending the return value to the reducers.


# Server communication

We can use the `redux-thunk` method to allow simple server communication by replacing the `setTimeout()` call from the previous example with a network call to the server:


~~~~~~~
import * as constants from 'constants/actionTypes';
import axios from 'axios';

const getRecipes = (limit = 100) => (dispatch) => {
  dispatch({ type: constants.FETCH_RECIPES_START, limit });

  axios.get(`recipes?limit=＄{ limit }`)
    .then(({ data }) => dispatch({type: constants.FETCH_RECIPES_DONE, data}))
    .catch(error => dispatch({type: constants.FETCH_RECIPES_ERROR, error}));
};

export getRecipes;
~~~~~~~

While this code might work for a very simple project, it will require a boilerplate for each API call we make. We discuss a more generic and cleaner approach to server communication in the Server Communication module.

Learn about server communication using redux-thunk.

Introduction to Redux

Basic Redux Implementation

Cloning a Redux Boilerplate

Complete Redux Project

Creating a Store

Decorating the Store

Actions and Action Creators

Redux Thunk

Redux-Actions Library

Reducers

Avoiding Mutations

Introduction to Middleware

Your First Middleware

Middleware

State Management

Keeping a Normalized State

Persistence State

Real-World State

Server Communication

Moving Code from Action Creators

Error Handling

Server Communication II

Transforming Data

Chaining Requests

Managing Side Effects

Messaging Patterns

WebSockets

WebSocket Authentication

Testing

Testing Action Creators

Async Action Creators

Testing Reducers

Testing Middleware

Testing Async Middleware

Integration Tests

Evolution Of Redux

Final Assessment

Server Communication

How does redux-thunk work?