So there are exceptions where you might fire actions as commands, the problem is that it is implicitly enforcing an imperative flow, as your action will know about where it is used, which doesn’t scale.

Now, the exception is, if you have an effect, that is triggered by an “action named as event”, that can trigger something specific such as login etc that is in the effect below, in that case I name the action as command, if the action is triggered from any other place than an effect, I name them as events always.

what’s wrong with this, actually I use actions as commands, like:
LoginWithEmailAndPassword(email: string, password: string)
to handle the login from the effects, also I have similar actions like:

loadStoreDataByDomain(url: string)
loadStoreDataByStoreId(storeId: string)

so the controller/brain is the effects, where it handles the http requests and update the store accordantly:
loginSuccess()
loadStoreSuccess()

could you please elaborate more on this point, like how to handle login without actions..
keeping mind that we want to hide/encapsulate the http requests & business logic from the components, and to handle them from the effects
thank you AGAIN!
:rose: