Skip to content
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

Optimistic updates #287

Closed
megamaddu opened this issue Jun 21, 2016 · 1 comment · Fixed by #336
Closed

Optimistic updates #287

megamaddu opened this issue Jun 21, 2016 · 1 comment · Fixed by #336

Comments

@megamaddu
Copy link

Client-side optimistic updates should work pretty seamlessly if there's a way to tell the mutation "here's the data to use until the response comes back". The trick will be figuring out how to get that into the current syntax and deciding how it gets undone in the event of a failure, since a failed server call probably can't be expected to reliably undo the optimistic update by sending down the opposite change (seeing how it failed, after all).

@stubailo
Copy link
Contributor

I think we can use one of the two, since the store is already implemented with Redux:

This would mean modifying how we handle the MUTATION_RESULT action, and adding an optimistic version that we roll back when the actual result comes back.

Do you have experience working with Redux? Perhaps you could help implement this!

@davidwoody davidwoody mentioned this issue Jun 29, 2016
6 tasks
jbaxleyiii pushed a commit that referenced this issue Oct 17, 2017
jbaxleyiii pushed a commit that referenced this issue Oct 18, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants