title: redux-toolkit state change in extraReducer does not initiate rerender
body: <p>I am trying to logout and purge the store at the same time, so on click I dispatch this:</p>
  
  <pre><code>dispatch({type: PURGE, key: 'root', result: () =&gt; { } });
  </code></pre>
  
  <p>Redux persist catches it, and reports purging the store. Great. 
  In another reducer I catch that dispatch, and remove my access token like this:</p>
  
  <pre><code>import { PURGE } from 'redux-persist/es/constants';
  
  const authSlice = createSlice({
    name: 'auth',
    initialState,
    reducers: {
      setAccessToken(state: AuthState, action: PayloadAction&lt;Auth&gt;): void {
        state.accessToken = action.payload.accessToken;
        state.expiresIn = action.payload.expiresIn;
      },
    },
    extraReducers: {
      [PURGE]: (state: AuthState, action: string): void =&gt; {
        state.accessToken = initialState.accessToken;
        state.expiresIn = initialState.expiresIn;
      },
    },
  });
  </code></pre>
  
  <p>The PURGE reducer actually is called, and modifies the state, but still no re-rendering happens. so redux must not pick that up. But according to the docs the Redux toolkit uses a Proxy object for the state and does a comparison to see if it's modified.</p>
  
  <p>Things I tried:</p>
  
  <pre><code>state = initialState;
  </code></pre>
  
  <p>and</p>
  
  <pre><code>state = { ...initialState };
  </code></pre>
  
  <p>Didn't work. The store works, and holds data, other actions work. How do I proceed?</p>
  
  <p>EDIT: Further debugging revealed that my own reducer was called BEFORE the redux-persist reducer, and redux-logger reported that my reducer did not change the state at all. </p>