Enable to use custom Query/Mutation/Subscription naming #54
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
|
👍👍 |
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.
This PR solves #27.
During development we also run into issue that our queries and mutations are named
RootQueryandRootMutation(which is by the way a very common practice) and this prevents us to use this tool. Renaming them is not an option since the types generated from them are used across many other projects and we can't change them.I tested these changes with our schema and it works great. Also it's a small, non-breaking change that would solve quite a huge issue so I hope this will become part of the library soon, otherwise the only way to use it is to fork it to our project and add those changes there.
Will be waiting for updates, thanks! 🤞