Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to mutate schema in-place #422

Open
roman-vanesyan opened this issue Jul 28, 2021 · 0 comments
Open

Add ability to mutate schema in-place #422

roman-vanesyan opened this issue Jul 28, 2021 · 0 comments

Comments

@roman-vanesyan
Copy link

roman-vanesyan commented Jul 28, 2021

Currently graphql-middleware uses @graphql-tools/schema package to actually apply schema modifications to the initially provided one (via addResolversToSchema function). Here

updateResolversInPlace: false,

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant