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



A common dilemma when using the API middleware approach is deciding whether the `onSuccess` parameter should be an action creator:

~~~~~~~
import { setUserData } from '../actions/users';

const fetchUser = id => ({
  type: API,
  payload: {
    url: `/user/${id}`,
    onSuccess: setUserData
  }
});
~~~~~~~

or a type constant:

~~~~~~~
import { SET_USER_DATA } from '../constants/actionTypes';

const fetchUser = id => ({
  type: API,
  payload: {
    url: `/user/${id}`,
    onSuccess: SET_USER_DATA
  }
});
~~~~~~~


The difference between these approaches is in the way the API middleware dispatches an action once a network request is resolved:

~~~~~~~
//Receiving an action creator
axios.get(url)
   .then(({ data }) => dispatch(onSuccess(data)));
~~~~~~~

~~~~~~~
// Receiving an action type
axios.get(url)
   .then(({ data }) => dispatch({ type: onSuccess, payload:  data }));
~~~~~~~

Both approaches have their pros and cons. Passing an action type makes actions serializable and thus easier to output to logs and debug visually. However, because this approach separates actions from network call results, it might be harder to follow the flow of side effects created by the actions.




A common dilemma when using the API middleware approach is deciding whether the `onSuccess` parameter should be an action creator:

~~~~~~~
import { setUserData } from '../actions/users';

const fetchUser = id => ({
  type: API,
  payload: {
    url: `/user/＄{id}`,
    onSuccess: setUserData
  }
});
~~~~~~~

or a type constant:

~~~~~~~
import { SET_USER_DATA } from '../constants/actionTypes';

const fetchUser = id => ({
  type: API,
  payload: {
    url: `/user/＄{id}`,
    onSuccess: SET_USER_DATA
  }
});
~~~~~~~


The difference between these approaches is in the way the API middleware dispatches an action once a network request is resolved:

~~~~~~~
//Receiving an action creator
axios.get(url)
   .then(({ data }) => dispatch(onSuccess(data)));
~~~~~~~

~~~~~~~
// Receiving an action type
axios.get(url)
   .then(({ data }) => dispatch({ type: onSuccess, payload:  data }));
~~~~~~~

Both approaches have their pros and cons. Passing an action type makes actions serializable and thus easier to output to logs and debug visually. However, because this approach separates actions from network call results, it might be harder to follow the flow of side effects created by the actions.


Let's discuss the possibilities of passing action creator or type constant to our functions.

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

Passing Functions or Strings