redux-operations does everything in a store enhancer, even async, so there’s no middleware involved. Since state location is dynamic and declarative, you could take a component framework like http://react-toolbox.com/, add a redux-operations wrapper to it, and you’ve got fresh components that have state resting in your redux store. Just think: a bootstrap-esque framework where the active tab #, shadow effect of the login button, etc is all your redux state… it don’t get more composable than that ;). I’ll be getting around to that in the next few months.

For point #2, are you talking about testing for async or testing for the flow through operations? I think it’s a good idea to whip a few tests & if you give me a couple examples of stuff you’d like to see in a github issue I’ll see what I can do. I’m still not sure what you mean by not declarative though, would love an example!