How to call an action in a different slice from a nested asynchronous action

I have a (nested) login() action which is inside an auth object/namespace and an updateLoading function that is not inside that namespace (it is called from other places in my app). Something like this:

const reducers = module.exports = {
    updateLoading: loading => state => ({
	loading
    }),
    auth: {
        login: () => (state, actions) => {
            actions.updateLoading(true)
	}
	// Do the login etc ...
    }, 
    // ...
}

Now, since login is asynchronous, I want it to call the updateLoading() while doing the http post request to the login API but the actions object that it receives contains only the actions that are inside the auth object/namespace.

Is it possible to call the upadeLoading action from inside auth.login ?

[spapas]

@JorgeBucaran no problem - as others have pointed out in this thread there are various ways this issue can be solved.

However, since most users trying to implement non-toy apps will probably stumble upon this problem, I recommend adding some mention of this problem and possible solutions with pros and cons to the docs (or maybe add another doc like best practices where problems like this would be discussed).

[spapas]

Yes I understand your argument about breaking up the state/actions to different modules but I don’t think that having an optional global_actions argument would do any harm - if people understand the consequences (their actions object have a specific structure) then why not use it and make their lives easier?

I also tried your fourth solution and it works really nice - although I agree that it feels a little “hackish” and is not very easy to understand.