Design Middleware implementation

[robwormald]

• as this is Rx powered, middleware will take a different form than Redux would.
• side effects vs no side effects
• sync vs async.
• etc

needs design

[fxck]

There's middleware and there's async... in redux, you use middleware - mainly - to get async working, you can use this or that or whatever, but the question is, do you even need the ability to write middlewares ... or you just need to support async out of the box.. it's the latter for me, at least for now.

..then again, maybe you've already got async figured out, I've seen this http://plnkr.co/edit/MYvlnPEMl5GFdFztGpcn?p=preview but I'm not sure if it's just a test or something final :)

[xgrommx]

Almost all cases can be covered via spawn or wrap. Like an Observable, Promise, thunk, scalar value, complicated Observable etc. Reactive-Extensions/RxJS#855 I made this method a very powerful. Also will be interesting Rx.Observable.when which is an implementation of Join Pattern @fxck @robwormald

[laurelnaiad]

Would not redux-saga's be a good fit for async behaviors/side-effects? Would redux-saga notice that it isn't working with a redux store? Would we be confined to the disassociated runSaga approach?

[robwormald]

See https://gist.github.com/tomkis1/8b3573ca9483d60c8b34 for a few ideas on an Rx version of Saga. I much prefer this style...

[robwormald]

this is initially implemented in 1.3.2 👍

[evanjmg]

To follow up, can I return promises or observables in my meta reducers? - I want to be able to save the state with using promises.