Jeff Auriemma

Thanks all, it seems that some commenters see this as a documentation issue and some see this as a source code issue. @thisfrontenddev what docs page would you recommend changing?

Thanks for that response @leepowelldev! In 3.7.4 we did ship a patch to the `useMutation` callbacks: https://github.com/apollographql/apollo-client/pull/10425 Does that help clear things up?

Hi @gurschitz 👋🏻 thanks for opening this issue! The team needs to triage this one further but we'll be taking a look soon. Thanks so much for the reproduction case...

Hi @ktsosno 👋🏻 I'm doing some housekeeping and transferred your feature request here. Thanks so much for your patience!

Thanks for opening this issue @maciesielka! I've put it on the agenda for an upcoming team meeting, we'll let you know once we've had a chance to triage a bit...

Okay I have an update for you @maciesielka! This is definitely an issue we'd want to fix but we also need to be careful not to introduce a performance regression,...

Hi @M1CK431 👋🏻 thanks for filing this issue! Without knowing more about your specific use case, this seems like a problem that can be solved via field and type policies....

Thanks for the quick reply @M1CK431. I'm struggling to find the words for why it seems "off" to want to deep clone the cache in this way, besides the potential...

Thanks @M1CK431 - I'll tag this as a feature request so others in the community can find and weigh in on it 🙏🏻

Hi @GokhanArik 👋🏻 just wondering if you saw @BoD's message above? The new cache may resolve your issue, let us know 🙏🏻