-
-
Notifications
You must be signed in to change notification settings - Fork 816
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
Ignore unmerged fields #6134
Ignore unmerged fields #6134
Conversation
🦋 Changeset detectedLatest commit: 4bf7835 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Benchmark Results
|
💻 Website PreviewThe latest changes are available as preview in: https://7ec8a639.graphql-tools.pages.dev |
02bcf3e
to
2a82186
Compare
🚀 Snapshot Release (
|
Package | Version | Info |
---|---|---|
@graphql-tools/delegate |
10.0.10-alpha-20240507100550-4bf783541466a6d38269f884d7499da67bcbc345 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/federation |
1.1.35-alpha-20240507100550-4bf783541466a6d38269f884d7499da67bcbc345 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/stitch |
9.2.8-alpha-20240507100550-4bf783541466a6d38269f884d7499da67bcbc345 |
npm ↗︎ unpkg ↗︎ |
If a field is not going to be used for type merging in the following calls, do not add it to the final query to the subgraph.
See the changeset for the example