Support GraphQL 1.6's multiplexed execution #55
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In GraphQL 1.6, @rmosolgo introduced the
Schema#multiplex
feature 🎉 which lets you execute multiple queries in one go. But it seems that it invokes the query instrumentation once per query, instead of just once, which causes theNestedError
to be raised. This change removes theNestedError
behavior.I'm opening this PR mainly as a discussion. I'm actually not sure what the ramifications are of allowing this nested behavior. But anywho, thoughts?