为什么使用Curry Redux中间件:状态=>下一个=>动作{}与(状态，下一个)=>行动 {}

Making the compose call in applyMiddleware:dispatch = compose(...middleware)(middlewareAPI , store.dispatch)推荐答案与Dan Abramov的讨论可以找到此处与此有关.他说，A discussion with Dan Abramov can be found here regarding this. He said, 我们本来可以做到的(存储，下一个)=>操作=>()，但我没有看到 一路走来的问题.您可能需要一些配置 稍后，此时选项=>(存储，下一个)=>操作=>()看起来 有点武断. We could have made it (store, next) => action => () but I don't see a problem with just going all the way. You might want some configuration later, at which point options => (store, next) => action => () looks kinda arbitrary.所以，没有必要咖喱参数.So no, it is not necessary to curry the parameters. 这篇关于为什么使用Curry Redux中间件:状态=>下一个=>动作{}与(状态，下一个)=>行动 {}的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！