Christer van der Meeren

Thanks! I'll have a look at that. I suggest we take further discussion on the actual PR, and see if we can't slowly shape it up into something that can...

@ahmad2smile I haven't used Redux.NET in at least a year (I'm rolling my own simple Redux store in F#). Perhaps someone else can help you?

Both works. I've seen viewmodels used; personally I just use the codebehind, because I don't need much logic in there for my app (and also I want to make it...

I've moved to F# (not really relevant for this comment) and am using a solution I find very clean and easily testable, which allows for unidirectional data flow of most...

For now, try using a pre-2.x.x version. AFAIK the only change 2.0.0 brought was .net standard compatibility. Note that I'm successfully using 2.0.0 with profile 7.

I agree that `ActionDispatched` is more fundamental than `StateChanged`. The state, after all, changes in response to an action dispatched to the reducers. It is also true that using `ActionDispatched`...

I agree that having both `StateChanged` and `ActionDispatched` seems the best solution – the former for reacting to state changes, and the latter as a powerful way of extending the...

`ActionDispatched` is a fairly low level concept that makes the store more extensible. It serves as the basis for an observable of actions that allows registering sagas using Rx, see...

It's important to note though that this does not replace middleware. This is for doing stuff with actions that have already reached the store and been dispatched. This is not...

It's true that we could pass some kind of `StateChangedEventArgs` that could include the action, but that's really then just `ActionChanged` under another name. > you should follow the standard...