You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be a good idea to allow events (or any any consumer) to wait until a dispatched action has been consumed, potentially by an effect.
e.g.
effects.register(kind,action,async({ dispatch })=>{awaitdispatch(turnOnComputer())// waits until the action is consumed, possibly by another effectdispatch(login())})
I think that this is a great idea. There are a lot of examples in our Skele apps where we do workarounds because this is not yet supported. It can be useful in the following cases:
Wait for a read refresh to finish, then do something
Push a new navigation scene, then do something
However, we should be careful about handling situations where there is no one to consume the action. I am guessing that the dispatch should then result with an exception.
It may be a good idea to allow events (or any any consumer) to wait until a dispatched action has been consumed, potentially by an effect.
e.g.
What do you think @andon, @bevkoski ?
The text was updated successfully, but these errors were encountered: