Make the test helpers compatible with nested fields #24
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.
Previously, a GraphQL document containing nested fields could not be tested if one of the values was null /
nil
. The library stringifies the expected response, coercingnil
to""
. Theassert_values_match
was not able to take into account the field being defined asnillable
because it wasn't aware of the nesting. This led to the below mismatch:This PR adds a new
assert_values_match
so that nested field definitions get recursively resolved.