Return the next action at the end of the middleware, as expected by redux

[tmarnet]

Redux is expecting middlewares to return the next action, if not some weird behavior could happen (it did in my case)

Source

[coveralls]

Coverage remained the same at 100.0% when pulling bb50774 on destinvp:add_return_middleware into dacca9a on mironov:master.

[mironov]

@ThomasMarnet Hey, thanks for the heads up! I've just released the new version with simplified middleware. Could you check if it works for you please?

[tmarnet]

Works for me 👌

But, if I may, now the order of the dispatched actions is reversed. Meaning if a LOAD action is intercepted by the middleware, it will only be dispatched after the SHOW one, you know what I'm saying ?
That's in fact the reason why you had to rewrite your tests, and also the reason why I had a constant containing the next(action) at the very top of the middleware which I was returning at the end. This way, I kept the actions' order you had before.

It's not blocking, you can keep it like that, or put it back like before. The result is nearly the same and it still works in both cases.

[mironov]

@ThomasMarnet Yeah, exactly. I think the way it works now is more straightforward. There's no reason to dispatch SHOW/HIDE actions after the initial action completes.

I'm closing this as of now. Please let me know if you encounter an issue with the new approach.