feat(query-planner): Include operationKind
and operationName
in FetchNode
s (backport)
#1609
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.
Backport of:
#1427
#1550 + #1568
This maintains parity in the query plan format with v2 by generating operation names for subgraph fetches. This also brings in the addition of
operationKind
out of convenience / maintaining parity since the changes are so closely related.cc @chrskrchr who I know was interested in this addition for v0.x and @lennyburdette as the implementor of the name generation