Re-resolve fragments when their calls change #146
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
steveluscher
force-pushed
the
re-resolve-given-changed-call
branch
from
1771de5 to
5ea96f8
Compare
steveluscher
force-pushed
the
re-resolve-given-changed-call
branch
from
5ea96f8 to
b3e374c
Compare
steveluscher
added a commit
that referenced
this pull request
Aug 27, 2015
Summary: Given a fragment with a range whose call is `first(1)` one moment, and `first(2)` the next, make sure that `GraphQLStoreQueryResolver::resolve()` re-resolves it. Fixes #120. Closes #146 Reviewed By: @josephsavona Differential Revision: D2372922
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.
Given a fragment with a range whose call is
first(1)one moment, andfirst(2)the next, make sure thatGraphQLStoreQueryResolver::resolve()re-resolves it.Fixes #120.