Hi there!

How to best handle side-effects of rtk queries? E.g. I have a query that checks whether a user is still logged in. When they get logged out, I would like to trigger a popup.
A naive approach could be:

function useAuth () {
  const {authData} = useAuthQuery();
  useEffect(() => {
    
  }, [authData]);
}

but that's not what useEffect is supposed to be used for. Another idea I had was to use a listener:

listenerMiddleware.startListening({
  predicate: (action) => action.type === 'auth/executeQuery/fulfilled' && action.meta.arg.endpointName === 'authStatus' && !action.payload.loggedIn,
  effect: (_action, listenerApi) => {
    listenerApi.dispatch(showLoggedOutPopUp());
  }
});

But I can't actually get the action whose type I'm referencing out of the api, so this looks like it is relying on implementation details.

What's the best approach? If the second one is of interest, would it make sense to expose these actions to be able to react to them? There is already ".internalActions", but this doesn't expose the query action in a way that can be reached, because the action itself is created via a thunk which isn't exposed.
If there is interest in something like this, I'm also happy to provide a PR (with a little guidance).