fragment args spec suggestions #1
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
yaacovCR
force-pushed
the
fragment-args-spec-suggestions
branch
from
7cb1898
to
e09d8fc
Compare
yaacovCR
force-pushed
the
fragment-args-spec-suggestions
branch
from
e09d8fc
to
b2546a0
Compare
yaacovCR
force-pushed
the
fragment-args-spec-suggestions
branch
2 times, most recently
from
da7743e
to
25512c5
Compare
yaacovCR
force-pushed
the
fragment-args-spec-suggestions
branch
from
25512c5
to
db40f80
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.
the execution suggestions depend on graphql#1039 just like incremental delivery
I am not sure about the nomenclature for the validation suggestions.
Basically, there are two ways that fragment args/variables can be unused:
(1) They can be unused within the fragment definition that defines the variable.
(2) They can be unused by any fragment spreads.