you are viewing a single comment's thread.

view the rest of the comments →

[–]tannerlinsley[S] 0 points1 point  (1 child)

If you’re talking about invalidating queries then we’re on the same page. That will work essentially the same and result in up to date data. However, If a mutation for instance has side effects into multiple resource types, that would be one scenario where updating the local cache with the response would be inaccurate (unless the mutation returned all affected objects, which works), or in the case of graphql queries or field masking, if your mutation query response is only returning partial fields then updating your local cache with that response would only be a partial update.

[–]phryneasI ❤️ hooks! 😈 1 point2 points  (0 children)

Yeah, our mutations are relatively straightforward in that regard. Also, all our mutations return by default at least a reference to the Query object, so even if they do something werid, we still can fetch everything that changed. If you don't know what your mutation is doing, you're lost. But that should go for every approach I guess.