How to use react redux middleware

This time I will show you how to use react redux middleware, and what are the precautions for using react redux middleware. The following is a practical case, let's take a look.

Students who have used react all know the existence of redux. Redux is a front-end warehouse used to store data and a framework for adding, deleting, modifying and checking the warehouse. It is not only applicable to react , also used in other front-end frameworks. Anyone who has studied the redux source code thinks that the source code is very sophisticated, and this blog post will introduce the processing of middleware in redux.

Before talking about redux middleware, let’s use two pictures to briefly introduce the basic principles of redux:

The picture shows the basic process of redux. I won’t go into details here.

Generally, not only redux is used in react, but also react-redux:

react-redux will not be detailed here.

redux middleware

Under normal circumstances, redux does not have the ability to handle asynchronous requests. Young communication is enhanced through indirection or adding middleware. In addition to the ability to dispatch, yes redux has asynchronous capabilities;

Generally speaking, there are two ways for redux to handle asynchronous processing: indirect method and middleware method;

Indirect method:

The indirect method is to customize the asynchronous behavior and retain the dispatch synchronization function.
Idea: The asynchronously returned result is stuffed into the action, and then synchronized to the reduce through dispatch, and then the state is changed;

demo:

request.get(API)
    .then(d => {
      store.dispatch(type: xxx, playload: d)
    })

This method does not destroy the synchronization mechanism of dispatch. It uses dispatch to synchronize data to the state. However, the disadvantage is that each call will write a long paragraph.

Middleware method

The core part of the middleware method is the high-order function applyMiddleWare provided by redux, which returns a brand new store object through multiple layers of calls. The only difference between the new store object and the original object is that dispatch has the asynchronous function;

Source code:

const applyMiddleWare = (...middlewares) => createStore => (reducer, initState) =>{
  const store = createStore(reducer, initState);
  const _dispatch = store.dispatch;
  const MiddleWareAPI = {
    getState: store.getState,
    dispatch: action => _dispatch(action)  1）
  };
  const chain = [];
  chain = middlewares.map(middleware => {middleware(MiddleWareAPI)}); 2）
  let dispatch = compose(...chain)(store.dispatch);  3）
  return {
    dispatch,
    ...store
  }
}

It is just a dozen lines of code, but it contains a lot of There are few subtleties. The blogger chose three of them to analyze their subtleties:

1) MiddleWareAPI is mainly inserted into middleware, and finally inserted into the action, so that the action can It has the ability to dispatch, and why anonymous functions are used here? The main reason is to keep the store in MiddleWareAPI.dispatch consistent with the store finally returned by applyMiddleWare. It should be noted that MiddleWareAPI.dispatch does not really change the state, it can be understood It is a bridge between action and middleware.

2) The change is to insert MiddleWareAPI into all middleware, and then return a function, and the form of middleware will be mentioned later.

3) This is the most subtle point. Compose will inject the chain array from right to left into the previous middleware, while store.dispatch will inject into the rightmost middleware. In fact, compose can be understood as a reduce function here.

eg:

M = [M1,M2,M3] ----> M1(M2(M3(store.dispatch)));

From here you can actually know what middleware looks like:

The basic form of middleware:

const MiddleWare = store => next => action => {
  ...
}

Parameter explanation:

1. store: In fact, it is MiddleWareAPI;

2. next: There are two situations here. If the middleware is changed, On the rightmost side of the middlewares array, next is store.dispatch; otherwise it is the return value of a middleware on the adjacent left (the closure function is the action => {} function);

3. action: It can be a function or an object containing a promise;

You may be a little confused here. The confusion may be the difference between next and store.dispatch. Clear;

Difference:

next (middleware on the far right): In fact, it is the dispatch that actually triggers the reducer and changes the state. The dispatch and state here are synchronized. ; the action here must be an object and cannot contain asynchronous information;

next (not the rightmost middleware): In fact, it is the function returned by the adjacent previous middleware (action => {.. .}); The action here is the action in next(action) of the upper-level middleware, and the action of the first middleware is the action in store.dispatch(action) in the project.

store.dispatch in middleware: It is actually used to plug in actions. It is understood here as the communication channel between actions and middleware.

Flow chart:

demo:

export const MiddleForTest = store => next => action => {
  if (typeof action === 'function') {
    action(store);
  } else {
    next(action);
  }
};

export const MiddleForTestTwo = store => next => action => {
  next(action);
};

export function AjaxAction(store) {
  setTimeout(function () {
    store.dispatch({
      type: 'up',
      playload: '异步信息'
    })
  }, 1000)
}

store.dispatch(AjaxAction);

said that you should have a general understanding of middleware here, let’s introduce it next Commonly used middleware and writing your own middleware.

redux-thunk:主要是适用于action是一个函数的情况，它是对原有的中间件模式再封装多一层，原则上是支持promise为主的action函数；

export function AjaxThunk (url, type) {
  return dispatch => {
    Ajax(url)
      .then(d => {
        dispatch({
          type,
          playload: d
        })
      })
  }
}
store.dispatch(AjaxThunk(url1, 'add'));

redux-promise:主要就是针对action对象，action对象是一个promise的异步请求函数：

它的大概实现思路是：

const promiseAction = store => next => action => {
    const {type, playload} = action;
    if (playload && typeof playload.then === 'function') {
      playload.then(result => {
        store.dispatch({type, playload: result});
      }).catch(e => {})
    } else {
      next(action);
    }
}

action = {
 type: 'xxx',
 playload: Ajax(url)
}

自定义中间件：很多时候网上的redux中间件可能不太符合项目中的需要，所以这时候可以自己写一套适合项目的中间件，以下指示本博主的一个demo，形式不唯一：

export const PromiseWares = store => next => action => {
  next({type: 'right', playload: 'loading'});
  if (typeof action === 'function') {
    const {dispatch} = store;
    action(dispatch);
  } else {
    const {type, playload} = action;
    if (playload && typeof playload.then === 'function') {
      playload.then(result => {
        store.dispatch({type, playload: result});
      }).catch(e => {})
    } else {
      next(action);
      next({type: 'right', playload: 'noLoading'});
    }
  }
};

相信看了本文案例你已经掌握了方法，更多精彩请关注php中文网其它相关文章！

推荐阅读：

怎样利用JS实现动态进度条

如何使用JS实现运算符重载

The above is the detailed content of How to use react redux middleware. For more information, please follow other related articles on the PHP Chinese website!