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
Currently graphql-middleware uses @graphql-tools/schema package to actually apply schema modifications to the initially provided one (via addResolversToSchema function). Here
it hard-codes addResolversToSchema to always produce a new schema. I'd like to make it configurable, so I can decide whether the initial schema should be modified in-place or a new one should be generated.
Currently
graphql-middleware
uses@graphql-tools/schema
package to actually apply schema modifications to the initially provided one (viaaddResolversToSchema
function). Heregraphql-middleware/src/middleware.ts
Line 45 in 8dc4590
it hard-codes
addResolversToSchema
to always produce a new schema. I'd like to make it configurable, so I can decide whether the initial schema should be modified in-place or a new one should be generated.This option would allow to hack around graphql-nexus/nexus#959 issue.
The text was updated successfully, but these errors were encountered: