-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clearing the client state using 'resetStore' #1509
Comments
This is currently intended behavior as far as I know. If |
There is no information in pre-resetStore - and I would prefer that over refetching queries and getting 403's because the token/cookies are invalid. The usecase makes it more difficult for us because this piece of our app is kind of a 'microservice' and logouts navigates away from it's own 'micro-domain' |
I think this should be fixed in react-apollo now, which was keeping the observable queries alive even when they weren't used any more. |
hi helfer, got a link to the PR ? |
@oavasilcai #1636 and the PR that references it in react-apollo. It should be shipped in |
Not sure if this is actually a bug but more of behaviour issue, we use
resetStore
to clear the state on user logout. However, active queries on that page are being sent onceresetStore
is called.The queries made require authentication on the backend, so once logout is made they respond with a 401.
I've already submitted a PR with a possible solution, just not sure how the apollo team wants to go about it: #1487
The text was updated successfully, but these errors were encountered: