Thread request context through to GraphQL executor #10
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.
This addresses the problem raised in #7; when
graphql()
is invoked, the current context value is not being passed to the executor (viacontext_value
).Here's a straightforward way to reproduce; if you run with and without the patch here, you'll see two different things
print
ed:and (using
WsLibSubscriptionServer
):This will print
None
and{'foo': 'bar'}
before and after this patch, respectively.