Using GraphQLRequest instead of DocumentNode for gql, execute, subscribe methods #556
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.
Breaking change:
gql
anddsl_gql
methods now returns aGraphQLRequest
instead of aDocumentNode
execute
andsubscribe
methods ofClient
and sessions now expects aGraphQLRequest
instead of aDocumentNode
A
GraphQLRequest
is an object which contains optionalvariable_values
andoperation_name
in addition to the document.Because of that double change, the simple code examples do not need to be changed, but if you're using external methods on the result from the gql method, like
print_ast
which expects a DocumentNode, then you will need to use thedocument
attribute of the request.Before:
After:
Deprecated variable_values and operation_name in execute and subscribe methods
The new way to add
variable_values
is to set it as a property of theGraphQLRequest
, and not as an argument ofexecute
orsubscribe
methods: