-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Introduce requireRootResolvers in GraphQL Modules preset #6796
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/theguild/graphql-code-generator/AKrKYPygw7A6vjtxcwsZAekqD9pU [Deployment for 1884baa failed] |
🦋 Changeset detectedLatest commit: 8f6ed82 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest changes of this PR are available as alpha in npm (based on the declared
|
1a4493a
to
ff30197
Compare
9ea19ea
to
7673256
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
The latest changes of this PR are available as alpha in npm (based on the declared
|
/theguild blog |
@charlypoly, issue saved for the blog! ⚡️ |
Before (and current default)
With
requireRootResolvers
enabled:It could help people to make sure all resolvers are defined (I think we enforce root-level resolvers in GraphQL Modules library as part of runtime check)