Field objects are allowed to be supplied without declaring blocks #37
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
Codecov Report
@@ Coverage Diff @@
## master #37 +/- ##
=========================================
Coverage 88.55% 88.55%
Complexity 68 68
=========================================
Files 16 16
Lines 166 166
Branches 28 28
=========================================
Hits 147 147
Misses 10 10
Partials 9 9
Continue to review full report at Codecov.
|
rudy-on-rails
force-pushed
the
rudy-on-rails/allow-field-object-declarations-to-not-use-blocks
branch
from
95c9802
to
fa91f3b
Compare
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.
GraphQL endpoints do not necessarily need to specify fields as arguments when a
mutationorqueryis received. Diverse implementations on the server-side will allow for returning non-standardized data formats, such as JSON, which breaks this library.Fixes: #31