preserve additional result body parameters in invocation

[eknuth]

Is your feature request related to a problem? Please describe.
Our spring boot graphql endpoint is stitched into a larger schema as a nested field. The unified graphql service passes data in the response body that we would like to access in our resolver. When I provide a custom graphql invocation, the response body has already been read and the variables have been lost.

Describe the solution you'd like
Preserve result body parameters in addition to query and variables. Particularly we are passed an extensions parameter that would need to be deserialized and read from the response body. From the invocation these data could be added to the context.

Describe alternatives you've considered
Not seeing any alternatives at the moment.

Additional context
Thank you for your consideration!

[oliemansm]

Can you provide example request/responses to clarify what you mean? Is this part of the GraphQL specification?