Ben Durrant

Hey there! This would fall under the idea of a tag system (see #11) and it's not something I'm entirely against, however it's not a high priority. Tags are difficult...

definitely the generic

this was addressed in https://github.com/reduxjs/redux-toolkit/pull/3187, and is already in the [v2.0 beta](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0-beta.0). Currently it's a breaking change (due to the new type parameter required by all the types), which is...

@Arbaaz234 that seems like a different issue - can you open it separately, ideally with a codesandbox reproduction/[replay](https://www.replay.io/)?

we can't help you without seeing your actual code, and like i said this is a separate issue. at a random guess, it sounds like you could be doing `middleware:...

please take this to [Reactiflux](https://www.reactiflux.com/) or open another issue/discussion. I will no longer take random guesses as to what your issue is on this completely separate issue.

for what it's worth, i've come to the realisation that `listenForCondition` could be implemented without the need for the trigger: ```ts /** * Attach a one-shot listener to the store,...

No, that's completely unrelated to this issue. This issue is talking about condition rejection actions, which would have `condition: true` in the meta. See [`dispatchConditionRejection`](https://redux-toolkit.js.org/api/createAsyncThunk#options). Your error is an actual...

That's what action.error gets set to when you use rejectWithValue inside of an async thunk, because the actual error is action.payload, as you can see.

please take it back to that thread - as I said, it's entirely unrelated to this issue 😉