[Question] Passing actions to next rather than dispatching

[codfish]

[Question] Passing actions to next rather than dispatching

[darthrellimnad]

Good question :). I ran into this early on as well, but eventually came to appreciate the current functionality, since passing to the next middleware can avoid the previous middleware in the chain, rather than always starting over from the top. We can always attach another middleware after redux-api-middleware to process the resulting FSAs, and dispatch a new action or perform a transform (if necessary) and pass along to next middleware. This avoids having the "request/response" FSAs from being passed to unnecessary middleware, like redux-api-middleware itself.

I often use redux-observable along with redux-api-middleware for larger scale things or with legacy rpc/rest apis, which you might also find useful for these sorts of use-cases :). Can get a little tricky for optimizations, but I added an RFC issue for "callable RSAA" utils which has helped me in my projects. If interested, here is that issue:

#216

[codfish]

BTW thanks for building & maintaining this, it's great and I use it on all my projects!

[codfish]

@darthrellimnad great, appreciate the thorough response