Saga | Saga pattern implementation in Kotlin build | Microservice library

If You don't use M1 based computer to build, You can comment "__apply_Xcode_12_5_M1_post_install_workaround(installer)" line in Your Podfile.

I'd recommend giving the official Redux Style Guide a read.

Generally: at this moment, there are 14818 redux-themed packages available on npm. It's pretty impossible to name them all ;)

But also, there are clear recommendations by the Redux team:

• use Redux Toolkit
• if you only need api data without further manual logic, use createApi form RTK-Query
• if you need manual logic attached to that, use createAsyncThunk or just thunks. Only if those are not enough, turn to other middlewares like saga
• sagas are very overused, most of the time not needed and add unneccesary complexity. We are currently building an action-listener-middleware that covers about 75% of the saga functionality with a simpler api (those 25% functionality left after that are the real saga use case, but probably only 2-5% of users ever need those).
  That said, most people would not even need that and could probably do everything they are using sagas for with thunks instead, which are much more simple.

There are also other libraries like redux-observable etc. Those have a non-deniable market share in the single-digit percentages, but if you are just getting started, go by the official recommendations.

Best get started by reading the official Redux Tutorial. It should cover 90% of all the Redux knowledge you'll ever need.

From what I can tell there seem to be few small issues,

1. In the success test, you are using onSuccess and onError in the action, however the saga implementation expects success and error properties instead.

2. In the error test, you are defining your token selector as:

"redux-saga-test-plan": "^4.0.1".

Option 1. Use withState:

For static state, you can just use the withState method to allow select effects to work.

Option 2. Use static provider

You can provide mock values in a terse manner via static providers. Pass in an array of tuple pairs (array pairs) into the provide method. For each pair, the first element should be a matcher for matching the effect and the second effect should be the mock value you want to provide.

E.g.

saga.ts:

Here is a flexbox sample of your code and need some change, good luck.

Try passing arguments like this:

The select effect creator accepts additional arguments after the selector function which are then send to the selector itself, so you can do this:

const person = yield select(makeGetPerson, id);

Docs: https://redux-saga.js.org/docs/api/#selectselector-args

When you cancel a saga, all sub tasks cancel. Example:

I think the problem is that both tests use the same reference of SessionReducer._initialState. When you pass it to the state in withReducer, it isn't cloned in any way and so you end up working with the same object in memory.

There is lots of way how to fix it, e.g. you can have a method instead of a property to create the initial object: