Replies: 1 comment
-
Anyone? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In one of our mutations we return a new id (which is used in our query key) for a product if you don't have permission to update the existing one (we effectively clone the existing product so the user can continue without affection the original product). The response of this PATCH call is the same as the GET response for this product, with only the id being different, but since the query key with that id hasn't been in the cache before, setQueryData/ensureQuery doesn't change the active/rendered query to the new one. Is there a way to set the active/rendered query to the one with the new id?
Beta Was this translation helpful? Give feedback.
All reactions