-
-
Notifications
You must be signed in to change notification settings - Fork 805
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
AggregateError errors are GraphQL located errors, not the AggregateError itself #6356
Conversation
🦋 Changeset detectedLatest commit: 1f25458 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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.14-alpha-20240718125408-1f254587937296241eb62326e217df8027a9c657 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-http |
1.1.5-alpha-20240718125408-1f254587937296241eb62326e217df8027a9c657 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/federation |
2.1.2-alpha-20240718125408-1f254587937296241eb62326e217df8027a9c657 |
npm ↗︎ unpkg ↗︎ |
💻 Website PreviewThe latest changes are available as preview in: https://4e342b14.graphql-tools.pages.dev |
Instead of transforming the AggregateError itself to a GraphQL located error.
This is because of two reasons: