We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When providing tags via callback like in example given in https://redux-toolkit.js.org/rtk-query/usage/automated-refetching#providing-errors-to-the-cache sets both UNAUTHORIZED and Post after user logs in (UNAUTHORIZED is not removed). I believe providesTags should ensure that only the result from the last callback should be in api.provided (old tags should be removed).
api.provided
The text was updated successfully, but these errors were encountered:
See #2721 and #2717 - this is already merged into the integration branch for the next release.
Sorry, something went wrong.
No branches or pull requests
When providing tags via callback like in example given in https://redux-toolkit.js.org/rtk-query/usage/automated-refetching#providing-errors-to-the-cache sets both UNAUTHORIZED and Post after user logs in (UNAUTHORIZED is not removed). I believe providesTags should ensure that only the result from the last callback should be in
api.provided
(old tags should be removed).The text was updated successfully, but these errors were encountered: