-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
child gets out of sync with parent #120
Comments
Sorry, I'm not sure I understand the problem exactly. What do you mean by "one behind" the view of the parent? Do you have examples of what the parents has, vs what the child has? |
If I do something like
to force the todo list to rebuild every time, the list will start to show one more item whenever the parent view gets more data. Without doing that, in order to get one more item to render, I need to increment $first twice. Then each additional increment gets one more, but behind where it should be. If I inspect the data the parent has during rendering, it has the desired items, but the child container doesn't get them. Looking at the fragments (that I believe it uses to extract from the data store or something) it has a fragment that looks like the previous query. |
We dug into this, and should have a fix for you soon. Thanks @ts-smith! |
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
ts-smith@0f2f827
When incrementing the $first variable while there are more unshown todos, the child (TodoList) seems to get a view of the data that is "one behind" the view of the parent (TodoApp).
The text was updated successfully, but these errors were encountered: