Test recursion avoidance correctly #29
Merged
Conversation
This file contains hidden or 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
leebyron
added a commit
that referenced
this pull request
Jul 7, 2015
Test recursion avoidance correctly
|
Great catch, thanks! |
|
Yes, that's correct. This is testing the behavior of non-verified queries, to ensure behavior is correct in the case a query is executed before being validated. If validated, the fragment recursion would have been caught before execution, as would the mistyped type information. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
DataTypeis unknown type, so...Fragfragment spread was ignored and recursion was not tested correctly.Additional question: is it intended to just ignore a fragment on the unknown type?