Anthony Miller

Okay thanks for following up. That still seems really odd to me, but seems like it IS happening. At some point, we're going to make another pass at a lot...

Sorry this question fell through the cracks @majda107. It was posted during the holidays and we must have just missed it. What you're asking for is definitely an intended use...

Looking into implementing the fix for the `removeObject(for key:)`. It is going to require a change to the `NormalizedCache` protocol, so that it returns the cache keys of the removed...

This sounds like a good addition to make. We can add it to our backlog, but we have a lot of other things to work on and it's probably not...

Thanks @tonyarnold! If you want to contribute, start by checking out our [Contributors Guide](https://github.com/apollographql/apollo-ios-dev/blob/main/CONTRIBUTING.md) to understand a bit about the development process. You'll need to clone the [`apollo-ios-dev`](https://github.com/apollographql/apollo-ios-dev) repo and...

I'm closing this issue due to inactivity. If this is still unresolved, feel free to provide more information and we can re-open this, or create a new issue.

I'm closing this issue due to inactivity. If this is still unresolved, feel free to provide more information and we can re-open this, or create a new issue.

I think that approach makes sense to me! Seems like an improvement on what I originally designed here.

Well, I've made progress in the [Edisonian sense](https://www.brainyquote.com/quotes/thomas_a_edison_132683). Which is to say, I've continued to rule out things that have don't solve the problem. I just recently had a meeting...

@pm-dev I cannot believe it... but I think I finally cracked it!!! This only works if you disable fragment field merging in your generated models, but I imagine that's not...