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
Is there support for returning an extensions object? I see in the ExecutionResponse that there is already code to add errors, data, and extensions to the response but I haven't found a way to add extensions to the response. I have tried accessing the context object in the @query annotated method to add extensions through the ExecutionInput object but it is too far down the chain of events at that point. Having a way for developers to add to the extensions object is useful for returning metadata to the client about the data and fields that are returned. In my case, a warning that a field is deprecated is very useful.
Graphql-java already has support for instrumentation so I think being able to hook into that functionality is a good route.
The text was updated successfully, but these errors were encountered:
Sounds good. Only that the value parameter should be a JsonValue, as it could also be primitive or an array. And maybe we should accept Object and convert it to json automatically.
We probably should also think about how to support extensions on the client side.
Is there support for returning an extensions object? I see in the ExecutionResponse that there is already code to add errors, data, and extensions to the response but I haven't found a way to add extensions to the response. I have tried accessing the context object in the @query annotated method to add extensions through the ExecutionInput object but it is too far down the chain of events at that point. Having a way for developers to add to the extensions object is useful for returning metadata to the client about the data and fields that are returned. In my case, a warning that a field is deprecated is very useful.
Graphql-java already has support for instrumentation so I think being able to hook into that functionality is a good route.
The text was updated successfully, but these errors were encountered: