Operation request which requires state information

I have run into a case quite frequently where I have an operation on a request which requires some state information before I can dispatch the request. So I run a select -> dispatching the request. However this causes me to have to dispatch 2 different actions: first we have to dispatch the action to run the saga, then we run the saga, then we call the request action.

The downside of this with redux-act is the user dispatches action1 but they have to watch for action2 on the store. Example:

// Call to run set feature saga
const setFeaturesAction = createAction(`set ${type}`);

const _setFeaturesAction = createAction(`set ${type} internal`, ({ map, [type]: features }) => {
  return {
    request: {
      url: '/v2/maps/operations/',
      method: 'post',
      data: formatRPCCall(`set${typeCapitalized}`, {
        map_id: map.id,
        features,
      })
    },
  };
}, ({ map, [type]: features }) => ({ map, features }));

// Get some stuff from state then run _setFeaturesAction.
const setFeaturesSaga = function* ({ payload }) {
  const { map } = yield select(state.maps);
  return yield put({ map, ...payload });
};

const reducer = requestsReducer({
  actionType: getFeaturesAction,
  // stuff and things...


  operations: {
    [_setFeaturesAction]: {},
  }
}, baseReducer);


// User dispatches
function mapStateToProps(state) {
  return {
    data: state.data,
    operation: state.operations._setFeaturesAction
  };
}

function mapDispatchToProps(dispatch) {
  return {
    runOp: () => {
      dispatch(setFeaturesAction)
    }
  }
}

From a user perspective its a bit awkward to know the difference between _setFeaturesAction and setFeaturesAction to use the store. Do you have any suggestions to improve this pattern?

[megawac]

Closed the PR because I want to think about the problem some more. I’m going to try both your solutions this week. I’ll close this off if I like it, otherwise you can toss it in the bucket 😃

[klis87]

Closing, I will add some recipies before version 1 once working on docs. To sum up use either thunk or onRequest interceptor, it would be also possible to implement it on the driver level