[StrawberryShake] Add support for graphql documents to be globbed from a different directory #7869
Conversation
This file contains 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
…m a different directory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of the changes (Less than 80 chars)
I've reimplemented the globbing functionality of
dotnet graphql generatecommand to use Microsoft.Extensions.FileSystemGlobbing. This will allow patterns from thedocumentsnode of the.graphqlrc.jsonfile to be retrieved from different directories.Today this is not possible:
With a
documentsnode in the .graphqlrc.json of../ProjectB/**.graphqlThis will allow clients and operations to be in different locations, and to share the operation files between different clients.