Consume data from RTQ in selector

[michalvadak]

I have a mutation with fixedCacheKey as I need to consume the response in multiple places throughout the app. I need to perform a lot of actions on the response, so it would be helpful if I could consume it in the selector. I am well aware that the selector would need to change if the response changes. That's why I'm asking whether this is the best approach, or whether I should remove the fixedCacheKey, save the response in the store on the first mutation call, and then consume it from there.

const selectTest = createSelector(
  (state: RootState) =>
    gameApi.endpoints.postV15GameBuyRound.select({
      requestId: undefined,
      fixedCacheKey: 'gameRoundV15',
    })(state),
  (state) => {
    return state.data;
  }
);

[markerikson]

If it's a fixedCacheKey, you can probably just simplify that down to state => state.api.mutations.gameRoundV15 . We don't have any plans to change the structure of the cache objects, and the fixedCacheKey guarantees that should be where it's stored.