-
-
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
Nested Computed Fields Edge Case #6437
Conversation
🦋 Changeset detectedLatest commit: e1f7976 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 |
🚀 Snapshot Release (
|
Package | Version | Info |
---|---|---|
@graphql-tools/delegate |
10.0.19-alpha-20240814092043-e1f7976c0ab9122da7b71c9ca741f261d3028bb8 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/federation |
2.2.7-alpha-20240814092043-e1f7976c0ab9122da7b71c9ca741f261d3028bb8 |
npm ↗︎ unpkg ↗︎ |
✅ Benchmark Results
|
💻 Website PreviewThe latest changes are available as preview in: https://344f6ea1.graphql-tools.pages.dev |
Fix the bug happens when a merged field is a computed field requires another computed field requires a field from the initial subschema.
In the following test case,
totalOrdersPrices
needsuserOrders
which needslastName
from initialQuery.user
.So the bug was skipping the dependencies of
userOrders
because it assumedlastName
already there by mistake.