fix: invalidate client using existing query key#617
Merged
LeadcodeDev merged 1 commit intomainfrom Dec 30, 2025
Merged
Conversation
Pass variables into onSuccess and derive the mutation's exact queryKey via window.tanstackApi.get(...).queryKey to ensure the correct cache entry is invalidated
LeadcodeDev
approved these changes
Dec 30, 2025
NathaelB
deleted the
547-floating-action-bar-does-not-disappear-after-client-update
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pass variables into onSuccess and derive the mutation's exact queryKey via window.tanstackApi.get(...).queryKey to ensure the correct cache entry is invalidated