Add support for InterfaceTypeDefinition #530
Closed
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
|
@simonljus Sorry I have not been able to read your PR for a long time. I will cherry-pick and merge them later on my end. |
|
Resolved conflict at #609 |
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.
Solves issue #474
Add config option
withInterfaceTypeto make validation schema generation ofInterfaceTypeDefinitionoptional.Log a warning if an unsupported
TargetKindis used in a GQL Schema. By default, unknown target types handle everything asScalar. If theScalaris unknown, an Exception will be thrown with an error message about the unknownScalar.The difference with
InterfaceTypeDefinitioncompared toObjectTypeDefinitionis the lack of__typename(andQuery,MutationandSubscriptionAdded test cases similar to some of the
withObjectTypetest cases.