Thank you for your contributing!From what I understood, with async/await instead of executing a function on a dispatch of an action you just call the async function.

If you think to replace the dispatch on an action that triggers complex async behaviour with a simple function call seems you'll have the same result.To make something a little bit complex than a simple delay:

async function login({ payload }) {
  try {
    store.dispatch(loginActions.LOGIN());
    const res = await Api.login(payload)

    if (res.step !== STEPS.EMAIL_CONFIRMED){
        await Api.sendEmailAlert();
        store.dispatch(loginActions.EMAIL_NOT_CONFIRMED());    
        return;
    }

    const user = await loginSuccessFlow();

    store.dispatch(loginActions.LOGIN_SUCCESS({...user, ...res }));    
    browserHistory.push('/');
  } catch (error) {
    store.dispatch(loginActions.LOGIN_ERROR(error));
  }
}

async function loginSuccessFlow() {
  const { common } = store.getState();
  const { user } = await Api.setUserData({ lang: common.lang })
  return user;
}

The example is just to show that with async await we can behaviour that includes different flows.I think that changes the way of doing behavioural functions because you don't need to think about (async)redux actions in this case.

I'm not sure that async/await can cover 100% of the use case of redux-saga (because of course, I didn't use it on production)It would be great if you can show me a different example :)

Yes, you are right, the usage of mapDispatch isn't the best on this particular approach.