Adds configuration file to support varying GraphQL schema file locations - #10
Merged
NeedleInAJayStack merged 4 commits intoAug 9, 2026
Conversation
NeedleInAJayStack
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds support for a configuration file named
graphql-generator-config.yaml. The only supported field today isschema, which is a list of filenames or directories under which GraphQL schemas are located. This allows isolating particular schemas for generation.It adds tests and documentation for this feature, and makes small additional improvements to the documentation.
Note: This makes breaking changes to the generator CLI. However since the CLI serves only to support the build plugin, the CLI is not considered to part of this package's public API so this is marked as a minor change.
Fixes #4