-
-
Notifications
You must be signed in to change notification settings - Fork 814
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
Federation: handle shared root fields in optimal way #6188
Conversation
🦋 Changeset detectedLatest commit: 302ba50 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 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
|
🚀 Snapshot Release (
|
Package | Version | Info |
---|---|---|
@graphql-tools/delegate |
10.0.11-alpha-20240517135643-302ba506c04c6e74f9caff133b380c5daa765d8f |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/federation |
1.1.36-alpha-20240517135643-302ba506c04c6e74f9caff133b380c5daa765d8f |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/stitch |
9.2.9-alpha-20240517135643-302ba506c04c6e74f9caff133b380c5daa765d8f |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/utils |
10.2.1-alpha-20240517135643-302ba506c04c6e74f9caff133b380c5daa765d8f |
npm ↗︎ unpkg ↗︎ |
💻 Website PreviewThe latest changes are available as preview in: https://0eb0ee46.graphql-tools.pages.dev |
If two different subschemas have the root field, use the same field to resolve missing fields instead of applying a type merging in advance
See the changesets for the other required changes