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



In single-page applications, the better UX practice is usually not to block the entire UI with one loading indicator but to show multiple localized indicators depending on different pending network requests. An example could be two independent loading indicators for movie details and reviews.

A simple solution to this problem would be adding a `label` property to our API action payload and having the API middleware pass it to `apiStart()` and `apiFinish()` actions:


~~~~~~~
const fetchMovie = (movieId) => ({
  type: API,
  payload: {
    url: `/movie/${movieId}`,
    onSuccess: setMovie,
    label: 'movie'
  }
});

const fetchComments = (movieId) => ({
  type: API,
  payload: {
    url: `/movie/${movieId}`,
    onSuccess: setReviews,
    label: 'reviews'
  }
});
~~~~~~~
The following code signals the spinner to stop running when a fetch request is made:

~~~~~~~
dispatch(apiStart(label));

axios.request({ url, method })
  .then(({ data }) => {
    // handle response
    dispatch(apiFinish(label));
  })
  .catch(error => {
    // handle errors
    dispatch(apiFinish(label));
  });
~~~~~~~




In single-page applications, the better UX practice is usually not to block the entire UI with one loading indicator but to show multiple localized indicators depending on different pending network requests. An example could be two independent loading indicators for movie details and reviews.

A simple solution to this problem would be adding a `label` property to our API action payload and having the API middleware pass it to `apiStart()` and `apiFinish()` actions:


~~~~~~~
const fetchMovie = (movieId) => ({
  type: API,
  payload: {
    url: `/movie/＄{movieId}`,
    onSuccess: setMovie,
    label: 'movie'
  }
});

const fetchComments = (movieId) => ({
  type: API,
  payload: {
    url: `/movie/＄{movieId}`,
    onSuccess: setReviews,
    label: 'reviews'
  }
});
~~~~~~~
The following code signals the spinner to stop running when a fetch request is made:

~~~~~~~
dispatch(apiStart(label));

axios.request({ url, method })
  .then(({ data }) => {
    // handle response
    dispatch(apiFinish(label));
  })
  .catch(error => {
    // handle errors
    dispatch(apiFinish(label));
  });
~~~~~~~


Learn how to implement multiple spinners.

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

Implementing Multiple Spinners