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.

Sign up for GitHub

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

Jump to bottom

Mutations are not properly propagated to parents #5

Open

nerdsupremacist opened this issue Mar 9, 2020 · 0 comments

Labels

Owner

nerdsupremacist commented Mar 9, 2020 •

edited

Loading

Currently you can change values of the GraphQL property wrapper after a mutation.

However, when the mutated value is in a Fragment, the change isn't propagated to the original dictionary from where the query originated from.

This is an issue in the following scenarios:

The Fragment is actually in a List and the view gets recycled: then it will change back to the original value at some point.
The Fragment and the Parent both use the same variables. Then they run out of sync with each other

This will most likely require a rewrite of a lot of the GraphQL Property Wrapper and the generated initializer code

nerdsupremacist added bug Client API labels

nerdsupremacist changed the title ~~Mutations are not propagated to parents~~ Mutations are not properly propagated to parents

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment