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 your feature request related to a problem? Please describe.
Because of the way how createSchemaForApollo works if you want to override Apollo Server's default field resolvers you can't do so in Apollo Schema options.
Describe the solution you'd like
Instead the easiest way to achieve the same result would be to pass your custom fieldResolver directly to the graphql execute function, which is called by createSchemaForApollo.
Describe alternatives you've considered
Additional context
My use case is very simple: a legacy application that mixes database entities managed directly by the ORM with GraphQL helpers that aim to reduce the load down the graph. Whenever makes sense to return these helpers the return type is an object/array with the entity and the helpers, otherwise it's just the Entity. The custom fieldResolver function looks at the type: if it's an entity it returns the default fieldResolver function, otherwise it looks for the fieldName in the info object and decides if to call the default fieldResolver function on the entity or on the helpers.
The text was updated successfully, but these errors were encountered:
createSchemaForApollo won't be supported anymore in 3.0 and fieldResolver can be emulated applying a custom directive in schemaBuilder, so I think this can be closed.
Is your feature request related to a problem? Please describe.
Because of the way how
createSchemaForApollo
works if you want to override Apollo Server's default field resolvers you can't do so in Apollo Schema options.Describe the solution you'd like
Instead the easiest way to achieve the same result would be to pass your custom
fieldResolver
directly to the graphqlexecute
function, which is called bycreateSchemaForApollo
.Describe alternatives you've considered
Additional context
My use case is very simple: a legacy application that mixes database entities managed directly by the ORM with GraphQL helpers that aim to reduce the load down the graph. Whenever makes sense to return these helpers the return type is an object/array with the entity and the helpers, otherwise it's just the Entity. The custom fieldResolver function looks at the type: if it's an entity it returns the default fieldResolver function, otherwise it looks for the fieldName in the
info
object and decides if to call the default fieldResolver function on the entity or on the helpers.The text was updated successfully, but these errors were encountered: