Skip to content
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

Use aggregate-error instead of CombinedError implementation to keep the content of errors #1646

Merged
merged 1 commit into from Jun 15, 2020

Conversation

ardatan
Copy link
Owner

@ardatan ardatan commented Jun 15, 2020

@theguild-bot
Copy link
Collaborator

theguild-bot commented Jun 15, 2020

The latest changes of this PR are available as alpha in npm: 6.0.10-alpha-17b8ef4.0

Quickly update your package.json by running:

npx match-version @graphql-tools 6.0.10-alpha-17b8ef4.0

@dotansimha dotansimha merged commit 17b8ef4 into master Jun 15, 2020
@dotansimha dotansimha deleted the use-aggregate-error branch June 15, 2020 12:53
@ardatan ardatan added the bug label Jun 15, 2020
@ardatan ardatan changed the title Use aggregate-error to keep the content of errors Use aggregate-error instead of CombinedError implementation to keep the content of errors Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants