You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the global object identification specification, the viewer pattern is a well established pattern in the GraphQL world.
To fetch additional fields on the viewer the query planner should check if there is a Query.viewer field on the targeted subgraph and use that to resolve the additional fields on the Viewer type.
What is actually happening?
The query plan generation fails with the error There must be a field resolver definition in this context!.
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered:
tobias-tengler
changed the title
Support viewer field convention
Can not select field from another subgraph on Viewer type returned in mutation payload
Feb 6, 2025
Product
Hot Chocolate
Version
15.0.1
Link to minimal reproduction
b837653
Steps to reproduce
Write a mutation that returns the viewer and selects fields on the viewer that are not available on the subgraph the mutation is on.
What is expected?
Similar to the global object identification specification, the viewer pattern is a well established pattern in the GraphQL world.
To fetch additional fields on the viewer the query planner should check if there is a
Query.viewer
field on the targeted subgraph and use that to resolve the additional fields on theViewer
type.What is actually happening?
The query plan generation fails with the error
There must be a field resolver definition in this context!
.Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: