redux-saga

开发文档 https://redux-saga.js.org/ https://redux-saga-in-chinese.js.org/ https://redux-actions.js.org/ 源码 代码已经上传到github中，欢迎star或者fork appstore-react-v2.0 redux-saga 一、介绍 之前异步处理用的是redux-thunk + redux-actions + redux-promise，但是随着ES6中Generator的出现，人们发现用Generator处理异步可以更简单。而redux-saga就是用Generator来处理异步。 redux-saga文档并没有说自己是处理异步的工具，而是说用来处理边际效应（side effects），这里的边际效应你可以理解为程序对外部的操作，比如请求后端，比如操作文件。 redux-saga同样是一个redux中间件，它的定位就是通过集中控制action，起到一个类似于MVC中控制器的效果。 同时它的语法使得复杂异步操作不会像promise那样出现很多then的情况，更容易进行各类测试。 二、 安装 npm install --save redux-saga 三、saga常用辅助函数 put、call、takeEvery、takeLatest 1、put和call

I am trying to test every scenarios my saga could follow, but i am not able to make happens the behaviors i want. This is pretty simple, i have a HTTP request (login), and i want to test the success and the failure cases by mocking my API method. But, it looks like the call effect doesn't fire my api function, i don't really get yet how it works, but i guess that the middleware is in charge of invoking the function, and since i don't go though the store on my test, i can't get the result. So my question is, how can you test your saga when you need to dispatch different actions (typically

redux-saga 对于redux-saga，网上的文章已经数不胜数，在这里重提redux-saga，主要是想记录一下最近使用redux-saga的一些考虑和看法，本文不会去讲解各个 Effect ，如有需要可查看 文档 。 在redux-saga官网中的解释是一个saga就像是应用程序中一个单独的线程，独自负责处理副作用。第一次读完这句话，心里并没有太多的思考。因此后续在项目中也爬了许多坑。在这里我们需要明确两点，saga如何像一个单独的线程，在项目中具体是什么样的？什么叫做副作用？ 首先来看两段示例代码： 代码一： ``` js // getInitialData获取初始化数据 handleFetchShopData 获取商品数据 function* initialAct() { try { const res = yield call(getInitialData) const { code, userType } = res if(code === '0'){ if(userType) { yield fork(handleFetchShopData, userType) } } } catch(err) { console.log('initialAct', err) } } function* handleFetchShopData(param) { // do

How do I access the redux state inside a saga function? Short answer: import { select } from 'redux-saga'; ... let data = yield select(stateSelectorFunction); NickGnd As @markerikson already says, redux-saga exposes a very useful API select() to invoke a selector on the state for getting some part of it available inside the saga. For your example a simple implementation could be: /* * Selector. The query depends by the state shape */ export const getProject = (state) => state.project // Saga export function* saveProjectTask() { while(true) { yield take(SAVE_PROJECT); let project = yield select

I have used Redux-Saga . Code written with it is easy to reason so far, except JS generator function is messing up my head from time to time. From my understanding, Redux-Observable can achieve the similar job that handles side effects but without using generator function. However, docs from Redux-Observable does not provide many opinions of why it is superior against Redux-Saga. I would want to know whether not using generator function is the only benefit of using Redux-Observable. And what could be the downsides, gotcha or compromises from using Redux-Observable instead of Redux-Saga? Thanks