[Question] How to organize complex scenarios

How would you organize complex scenarios involving multiple async stuff and multiple action types?

With redux-saga its superb easy once one gets comfortable with generators and with redux-observable for a skillful observable user it should be quite easy too (although didnt use the latter personally).

Wondering how to orchestrating smth more complex would look like with the proposed approach of those self-contained descriptive actions in redux-pack.

Would be cool if such example be in the docs.

Nice lib nonetheless!

[sorodrigo]

@divyanshutomar

Thanks for the wonderful library.It really helps in writing more maintainable code. So I am stuck in a situation where I need to dispatch two actions one after another wherein a part (id of the newly created entity) of the response from first API call (POST request) is used as request data for the second API call (Another POST request that uses the retrieved id ). How do you deal with such scenarios?

I think maybe a good solution is to chain the promises given that this is a transaction one thing shouldn’t update the state without the other. So this could be done in the following way:

const getFooAndThenGetBar = async () => {
  const foo = await API.getFoo();
  const bar = await API.getBar();
  return { foo, bar };
}

export const doSomething = () => ({
  type: FOO_AND_BAR,
  promise: getFooAndThenGetBar(),
})

Then you can actually listen for FOO_AND_BAR in the 2 reducers that interest you.

[morgs32]

@lelandrichardson it would seem to me that your comment is more than an escape hatch. It makes the onSuccess and onFailure callbacks redundant. More importantly it is easier to test than those callbacks. Do you agree? Is there anything else to consider before I implement the “escape hatch” everywhere in my app?

Thanks for this library by the way.