-
-
Notifications
You must be signed in to change notification settings - Fork 810
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
Isolate computed fields return objects only if not referenced from other, non-isolated, objects #6543
base: master
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 71773b3 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
|
🚀 Snapshot Release (
|
Package | Version | Info |
---|---|---|
@graphql-tools/federation |
2.2.11-alpha-20241001170715-71773b38b5fe7e2b79e03e2e1fbb405d85fe1abf |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/stitch |
9.2.11-alpha-20241001170715-71773b38b5fe7e2b79e03e2e1fbb405d85fe1abf |
npm ↗︎ unpkg ↗︎ |
💻 Website PreviewThe latest changes are available as preview in: https://495fa957.graphql-tools.pages.dev |
When isolating the
User.requiresField
from the following schemathe
SomeRequiredType
should not be isolated because it is referenced from another, non-isolated, objectSomeTypeWithDisappearingField
.TODO
isolateComputedFieldsTransformer > with composite return type > return type is unmerged type
failing?