feat: adds emitSchemaFile option to GraphQLServer config #8032
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Matthew Schnee matthew.schnee@bambee.com
This PR updates the options for
GraphQLServerto supply the optionalemitSchemaFileoption. This is the same configuration used byTypeGraphQL's buildSchemamethod.Note that this is the basic, naïve implementation that TypeGraphQL itself uses. For a full schema including support for custom directives, using
GraphQLServer.exportGraphqlSpecmay be preferable.Checklist
npm testpasses on your machinepackages/cliwere updatedexamples/*were updated👉 Check out how to submit a PR 👈