Christer van der Meeren

Created a PR for this at #64 so we have some code to look at.

@dcolthorp It should be exception safe now. Calling `Dispatch` (on any store) or ` await DispatchAsync()` (on `AwaitableStore`) will 1) bubble up the exception, and 2) make sure that the...

I've updated the initial comment with more information. @dcolthorp Regarding https://github.com/GuillaumeSalles/redux.NET/issues/47#issuecomment-290535579 and your mention of `TakeLatest`: I tried experimenting, but couldn't find a solution that was simpler than simply letting...

Are you suggesting that we require the reducer(s) to specify the initial state? How exactly would this work in practice?

I don't think reducers should specify the initial state, because that would preclude them from using the "sentinel" value, e.g. `null`. That is, if the reducer gets `previousState = null`...

Oh, I see - it's only if the actual state objects are null that the default state (for that state object, e.g. `AState`) is returned. I have absolutely no problem...

I don't really know what the issue is here, but it seems the core of it is that something akin to a ListView is fully re-rendered even though only part...

I have a middleware that simply persists the few things I need. For example, when I dispatch a `SignInSuccessfulAction { Token = "..." }`, the action is picked up by...

More info: I came across this while trying to implement “listener middleware”, according to Alex Reardon's post [The ‘middleware listener’ pattern: better asynchronous actions in Redux](https://medium.com/@alexandereardon/the-middleware-listener-pattern-better-asynchronous-actions-in-redux-16164fb6186f#.bs2rzwuuf). To me this seems...

After some more thought and investigation, allow me to partially answer my own question: The return value from the middlewares “bubbles up” through the middleware stack, and is ultimately accessible...