Solving issue #31 #35
Open
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
This reverts commit 82432e6 Sorry, my dependencies were not updated, so I got other output... My changes were wrong, so I reverted them
|
@cmizzi Happy new year! Can you please merge this PR? |
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.
Hi.
As I already described in my issue #31, almost all helper tools for working with GraphQL claiming at
__typenameon InputObjects, so I just renamed it to_morphType. With this change it is directly clear, what this field means, and it also don't use any naming reserved by GraphQL anymore.Though I have to mention - this PR has brake-changes to some users, if they already used
__typenameon input.