-
Notifications
You must be signed in to change notification settings - Fork 64
fix: Local cache mutation generation when field merging disabled #654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Local cache mutation generation when field merging disabled #654
Conversation
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: da0721188710ec689bb12df0 |
✅ Deploy Preview for apollo-ios-docc canceled.
|
@BobaFetters - take a look at this one too if you'd like. I'll wait for @AnthonyMDev to review too before merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Code looks good to me, just some suggestions for the tests.
We're going to be handling the propagating of mutable status to fragments in a separate PR right?
Co-authored-by: Anthony Miller <[email protected]>
…m:apollographql/apollo-ios-dev into fix/fieldmerging-for-local-cache-mutation
OK @AnthonyMDev - ready for another review. |
Correct. I'm working on that one now. It'll be layered on top of this PR but this one can be merged before. I'd like to get them both merged before publishing the next release though. |
1b1661ba fix: Local cache mutation generation when field merging disabled (#654) git-subtree-dir: apollo-ios-codegen git-subtree-split: 1b1661ba166f6cbb857c003d016e5891f4a6c554
…ation when field merging disabled git-subtree-dir: apollo-ios-codegen git-subtree-mainline: 9c9efcc git-subtree-split: 1b1661ba166f6cbb857c003d016e5891f4a6c554
Fixes apollographql/apollo-ios#3554
The full set of selection set initializers must always be generated for local cache mutation operations and fragments. Before this change using a
fieldMerging
policy of anything other thannone
would generate local cache mutations but they could not be initialized and did not contain all the correct merged fields.