Jeff Auriemma

I attempted to resolve the merge conflicts here. I'll self-review this later in the week and add a changeset file as well.

Hi all, I'm doing some housekeeping and came across this issue. Reading through the conversation above, per @benjamn's [comment](https://github.com/apollographql/apollo-client/issues/9137#issuecomment-1116148425) this is the intended behavior. Thanks all for your thoughts and...

Hi @mccraveiro - I agree that this issue should be closed as we don't plan to change this behavior at this time. Thanks so much all for weighing in! If...

Thanks for your patience folks, could someone share some code snippets so we can help narrow down the issue here? I'm also wondering whether the behavior is the same if...

@dylanwulf is correct - updating the cache can be done through a variety of methods but directly mutating the object is not one of them. This has been the case...

Hi all, closing this issue it appears that this issue is resolved as of the 3.7 release. Please let us know if you need further support 🙏🏻

The Apollo Client maintainers are also interested in helping out. We have a in-person get-together that would likely prevent us from attending the 28 Feb WG meeting but are looking...

It's a one-time conflict

Hi @bluepichu 👋🏻 thanks for opening this issue and thanks for your patience. First, it's totally understandable that a user would expect `possibleTypes` to factor into a `toReference` so thanks...

@metrue see https://github.com/apollographql/apollo-client/pull/4154 for more info. Thanks!