在没有redux出来以前,父组件和子组件之间,平行组件之间传递和修改状态,须要将状态和修改状态的方法逐级往下传,组件嵌套过深则很容易出现管理混乱的问题。因此redux就是为了解决状态管理而诞生的。 react
//用来建立Store function createStore(reducer){} // 抽离出不一样的type调用dispatch函数的复用部分 function bindActionCreators(actions,dispatch){} // 合并reducer function combineReducers (reducers){} // 使用中间件造成一个新的dispatch覆盖原来的dispatch,并返回store function applyMiddleware (...middlewares){} //合并中间件 function compose(...args){} export { createStore, bindActionCreators, combineReducers, compose, applyMiddleware } 复制代码
function createStore(reducer){ let state; //存放状态 let listeners = []; //存放订阅的回调 function dispath(action){ state = reducer(state, action); // 调用reducer返回新的state listeners.forEach(fn=>fn()); // 发布全部订阅的回调 } // 派发初始动做,type为reducer中没有的类型,目的是初始化状态为用户设置的状态 dispatch({type:'@INIT'}); function getState(){ // 暴露的state属性不但愿别人能改,改了也不会影响原有的状态 return JSON.parse(JSON.stringify(state)); } function subscribe(fn){ //订阅回调,并返回一个从listeners删除回调的函数 listeners.push(fn); return ()=>{listeners = listeners.filter(l=>l!=fn)}; } } return { getState, dispatch, subscribe } } 复制代码
为了理解上面的东西,看下面的用例:redux
let initState = { title: { color: "red", text: "kbz" } }; function reducer(state = initState, action) { switch (action.type) { case "CHANGE_TITLE_COLOR": return { ...state, title: { ...state.title, color: action.color } }; break; case "CHANGE_TITLE_TEXT": return { ...state, content: { ...state.title, text: action.text } }; break; } return state; } let store = createStore(reducer); let unsubcribe = store.subscribe(function() { console.log(store.getState().title.color); }); setTimeout(() => { store.dispatch({ type: "CHANGE_TITLE_COLOR", color: "yellow" }); }, 1000); setTimeout(() => { unsubcribe(); store.dispatch({ type: "CHANGE_TITLE_COLOR", color: "blue" }); }, 2000); 复制代码
在建立组件的时候,组件应该是存粹的,使用store.dispatch等其它变量,须要根据状况而区别的引入不一样的变量,最好使用state或者props,因此须要将action和dispatch抽离封装而后赋予到组件的prop上promise
//action-types.js export const ADD = 'ADD'; export const MINUS = 'MINUS'; 复制代码
//actions.js import * as types from '../action-types'; let actions = { add(count){ return {type:types.ADD,count} }, minus(count){ return {type:types.MINUS,count} } } export default actions 复制代码
function bindActionCreators(actions,dispatch){ let obj = {} for(let key in actions){ obj[key] = (...args)=>dispatch(actions[key](...args)) } return obj; } 复制代码
import React,{Component} from 'react'; import {render} from 'react-dom'; import Counter from './components/Counter'; import {bindActionCreators} from 'redux'; import store from './store'; inmport action form './action' let props= bindActionCreators(actions,store.dispatch) render(<Counter {...props}></Counter>,window.root); 复制代码
为了更好的模块化管理,能够将每一个组件的reducer分开来建立,而后再经过combineReducers将全部的reducer合并起来,其原理就是建立一个函数,dispatch的时候将全部reducer都执行一次bash
function combineReducers (reducers){ //返回一个总的totalReducer,和全部的reducer同样接收state和action return (state={},action)=>{ // totalState登记每个组件的state // 遍历执行全部的reducer,将返回的state从新登记在totalState中 let obj = {}; for(let key in reducers){ obj[key] = reducers[key](state[key],action) } return obj; } } 复制代码
中间件原理:在原来的dispatch方法外包装一层函数,扩展其余功能,又能保证原来功能的使用。markdown
// 打印日志中间件 let reduxLogger = (store)=>(dispatch)=>(action)=>{ console.log('prev',store.getState()); dispatch(action) console.log('next',store.getState()); } // let reduxThunk = (store)=>(dispatch)=>(action)=>{ // 若是是函数将正真的dispatch传给用户,用户抉择是否要派发 if(typeof action === 'function'){ return action(dispatch,store.getState); } dispatch(action); // 直接把对象派发便可 } let reduxPromise = (store)=>(dispatch)=>(action)=>{ // 判断当前action是否是一个promise,若是是promise就执行,执行的时候只会管成功的结果 if( action.then &&typeof(action.then) == 'function'){ return action.then(dispatch); }else if(action.payload && action.payload.then){ //action.payload是否为promise return action.payload.then(data=>{ dispatch({...action,payload:data}); },err=>{ dispatch({...action,payload:err}); return Promise.reject(err); // 对外抛出错误 }) } return dispatch(action); } 复制代码
let applyMiddleware = (middleware)=> (createStore)=> (reducer)=>{ let store = createStore(reducer); // 返回新的dispatchL:(action)=>{xxxxxx} let fn = middleware(store); let newDispatch = fn(store.dispatch); //覆盖原有的dispatch,返回{getState,dispatch:newDispatch,subscribe} return {...store,dispatch:newDispatch}; } // 典型的柯里化,把多个middleware连起来,后面compose会介绍 export default applyMiddleware(reduxLogger)(createStore)(reducer); 复制代码
项目中使用的插件不止一个,在使用多个插件的状况下,须要使用一个方法将多个插件合并成一个。react-router
function add(a,b){ return a+b; } function toUpperCase(str){ return str.toUpperCase(); } function len(str){ return str.length } function compose(...args){ return args.reduce((a,b)=>{(...args)=>a(b(...args))}); } compose(len,toUpperCase,add)(a,b); //(a,b) => len(toUpperCase(add(a,b))) 复制代码
a | b | 返回函数 |
---|---|---|
len | toUpperCase | (...args)=>len(toUpperCase(...args)) |
(...args)=>{len(toUpperCase(...args)} | add | (...args)=>len(toUpperCase(add(...args))) |
let reduxLogger = (store)=>(dispatch)=>(action)=>{ console.log('prev',store.getState()); dispatch(action) console.log('next',store.getState()); } let applyMiddleware = (...middlewares)=> (createStore)=> (reducer)=>{ let store = createStore(reducer); let fns = middlewares.map(middleware=>{ return middleware(store) //返回的函数接受disopatch用于在原来的基础上扩展 }); // compose(fn1,fn2)(store.dispatch) //fn执行返回一个新的包装dispatch函数传给fn1 let newDispatch = compose(...fns)(store.dispatch); return {...store,dispatch:newDispatch}; //将合并后的dispatch覆盖原来的最初的dispatch } function compose(...args){ return args.reduce((a,b)=>((...args)=>a(b(...args)))); } 复制代码
function createStore(reducer,fn) { let state; let listeners = []; let dispatch = (action) => { state = reducer(state,action); listeners.forEach(fn=>fn()); } dispatch({type:'@INIT'}); // createStore(reducer,applyMiddleware(...middlewares))一步到位 // 在内部使用applyMiddleware(...middlewares)(createStore)(reducer) if(typeof fn === 'function'){ return fn(createStore)(reducer); } let getState = ()=> JSON.parse(JSON.stringify(state)); let subscribe = (fn)=>{ listeners.push(fn); return ()=>{ listeners = listeners.filter(l=>l!=fn); } } return {getState,subscribe,dispatch} } function bindActionCreators(actions,dispatch){ let obj = {} for(let key in actions){ obj[key] = (...args)=>dispatch(actions[key](...args)) } return obj; } let combineReducers = (reducers)=>{ return (state={},action)=>{ let obj = {} for(let key in reducers){ obj[key] = reducers[key](state[key],action) } return obj; } } let applyMiddleware = (...middlewares)=> (createStore)=> (reducer)=>{ let store = createStore(reducer); let fns = middlewares.map(middleware=>{ return middleware(store) }); let newDispatch = compose(...fns)(store.dispatch); return {...store,dispatch:newDispatch}; } function compose(...args){ return args.reduce((a,b)=>((...args)=>a(b(...args)))); } export { createStore, bindActionCreators, combineReducers, compose, applyMiddleware } 复制代码
Redux是一款状态管理库,而且提供了react-redux库来与React亲密配合,这二者的关系以下图: app
import React,{Component} from 'react'; import {bindActionCreators} from './redux' let Context = React.createContext(); //将store挂载在contex上,供嵌套组件使用 class Provider extends Component{} // connect的做用就是获取store,子组件获取contex上的store let connect = (mapStateToProps,mapDispatchToProp)=>{} export { Provider, connect } 复制代码
React会提供一个createContext的API,调用它会生成一个Context,里面包含了Provider组件和Consume组件,Provider提供一个状态供跨组件使用,须要使用状态的组件只要嵌套在Consume中就获取Provider提供的状态。让react用起来更驾轻就熟——(react基础解析)里面有介绍,这里不赘述。框架
let Context = React.createContext(); class Provider extends Component{ // 将React-redux中的Provide包装了react提供的API生成的Context.Provider //<Provider store={xxxx}></Provider>,将store挂载在contex上 render(){ return <Context.Provider value={{store:this.props.store}}> {this.props.children} //子组件 </Context.Provider> } } 复制代码
既然有挂载store,就必然有子组件获取store,connect的做用就是获取提供好的storedom
//调用方法:connect(mapStateToProps,mapDispatchToProp)(Com) // connect是一个高阶组件,调用后的返回一个组件 let connect = (mapStateToProps,mapDispatchToProp)=>(Com) =>{ return ()=>{ // 高阶组件的特色就是把组件中公用的逻辑抽取来,返回一个通过处理的组件 class Proxy extends Component{ state = mapStateToProps(this.props.store.getState()) componentWillMount(){ this.unsub = this.props.store.subscribe(()=>{ this.setState(mapStateToProps(this.props.store.getState())) }) } componentWillUmount(){ this.unsub() } //mapStateToProps就是将state中的部分或所有状态映射到须要的组件中做为其props //mapDispatchToProp就是将action中已经绑定成dispatch形式的action按需求映射到须要的组件做为其props render(){ let b if(typeof mapDispatchToProp === 'function'){ b = mapDispatchToProp(this.props.store.dispatch); }else{ // bindActionCreators把直接将全部action的绑定成diapatch(action)形式组成一个对象 b = bindActionCreators(mapDispatchToProp,this.props.store.dispatch) } //将全部的state和修改state的方法以props的方式传入 return <Com {...this.state} {...b}></Com> } } //调用Consumer将获取到的store传给包装Com的Proxy return <Context.Consumer> {({store})=>{ return <Proxy store={store}></Proxy> }} </Context.Consumer> } } 复制代码
用例:ide
import React,{Component} from 'react'; import actions from '../store/actions/counter'; import {connect} from 'react-redux'; class Counter extends Component{ render(){ return (<div> <button onClick={()=>{ this.props.add(2); }}>+</button> {this.props.number} <button onClick={()=>{ this.props.minus(2); }}>-</button> </div>) } } // mapStateToProps用户本身定义须要的状态 let mapStateToProps = (state)=>{ return {number:state.counter.number} } // action也是用户本身定义的,能够是函数能够是对象 // 若是传递过来的不是方法是对象,会把这个对象自动用bindActionCreators包装好 export default connect(mapStateToProps,actions)(Counter); 复制代码
我的使用一种框架时总有一种想知道为啥这样用的强迫症,否则用框架用的不舒服,不要求从源码上知道其原理,可是必须得从心理上说服本身。