Replies: 1 comment
-
Our use case comes from our use of the graphql-tools project https://www.graphql-tools.com/docs/generate-schema/#makeexecutableschemaoptions. I assume this is not an uncommon case |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a setup where we keep multiple .graphql files and are then stitched together this is problematic as the current graphql inspector GitHub action only supports a single schema at a time. In addition to introducing repetition in my workflow file I also run into cases where a type defined to in a common .graphql file is referred to in another
What I'd like to be able to do is to leverage a path pattern in the
schema
input instead which will consolidate then evaluate any schema changes in aggregateThis would solve both the repetition as well as the current limitation of graphql inspector not being able to resolve types defined in other files.
Beta Was this translation helpful? Give feedback.
All reactions