SubscribeToAction with NavigateTo throws an exception about fluxor HOT 4 CLOSED

That's very helpful; thanks. I see that this can be resolved by adding either an Effect class or an [EffectMethod] flagged method within my component (which is the option I'll use).

Do you think that the ActionAsubscriber Notify method should be protected from this reentrancy problem though?

(And thanks for the work on this library.)

from fluxor.

I appreciate your thoughts - thank you.

from fluxor.

This looks like the behaviour I would expect. Instead, add an effect that dispatches a GoAction.

from fluxor.

I'll have to think about whether or not to change the loop. The change should happen in an effect.

I would put the effect method in with my store, not in the component. They should be kept separate.

And if you don't take my advice, at least make it a static method so Fluxor doesn't create an instance of your component.

from fluxor.