Actions Are Called Twice

Very cool library, I like the approach. Thanks for building and OSing it!

I’ve swapped in redux-pack for redux-thunk and rewritten an action called getBroadcasts from this redux-thunk action:

export function getBroadcasts() {
  return async (dispatch) => {
    dispatch({ type: 'GET_BROADCASTS_INITIATED' });

    try {
      const { data: { results } } = await api.get('/broadcasts');
      dispatch({ type: 'GET_BROADCASTS_SUCCEEDED', payload: results });
    } catch (error) {
      dispatch({ type: 'GET_BROADCASTS_FAILED', payload: error });
    }
  };
}

to this redux-pack action:

export function getBroadcasts() {
  return {
    type: 'GET_BROADCASTS',
    promise: api.get('/broadcasts')
  }
}

What I observe in the console when the relevant page loads is that while the redux-thunk action was called only once:

the redux-pack action is called twice, and returns once with an undefined payload, and once with a successful payload:

I assume this is expected behavior, I just wanted to confirm.

[evandavis]

It looks like there are intentionally 2 dispatches, on start and then on one of success or failure.

The nice part of having the 3-phase action (old way) is that you can have other reducers react to those actions. I think you lose that here, but maybe I’m missing something?

[fredguest]

Closing as this has been confirmed as expected behavior. Thanks for the discussion!