Skip to content

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

calvincestari
Copy link
Member

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 than none would generate local cache mutations but they could not be initialized and did not contain all the correct merged fields.

@svc-apollo-docs
Copy link
Collaborator

svc-apollo-docs commented May 16, 2025

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: e2a1514956881737ae1f174b

Copy link

netlify bot commented May 16, 2025

Deploy Preview for apollo-ios-docc canceled.

Name Link
🔨 Latest commit 00cca02
🔍 Latest deploy log https://app.netlify.com/projects/apollo-ios-docc/deploys/6827aec321071c0008884f42

@calvincestari calvincestari requested a review from AnthonyMDev May 16, 2025 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Non-all field merging causes selection set initializer to stop being generated for local cache mutations
2 participants