News for hackers. Stuff that matters.

A comment on Trello clone with Phoenix and React – 5-part tutorial. Parent comment

Re:Trello clone with Phoenix and React – 5-part tutorial by eric_bullington on Saturday January 23, 2016 @09:33AM (#10958491)
> And you need to have reliable 'rollbacks' on the client when server rejects the action for some reason....'ve solved all these problems eventually, but it took much more time for me than building the happy path.

I'm sure you figured this out, but having an immutable data structure at the root of your React application is great for rollbacks. And then maintain an array with a reference to the various data structures, however deep you need (within reason), and pop or push them as needed to rollback/roll forward.

[ Parent | on HN ]
Re:Trello clone with Phoenix and React – 5-part tutorial by hakanderyal on Saturday January 23, 2016 @09:38AM (#10958500)
Yes, I'm using Redux, and never modify the state. But I also needed to rollback only the rejected action, and keep the rest of the actions that user did after the rejected action intact. That presented a whole lot of different edge cases.

I created a solution based on redux-optimist[1], modified to my apps specific needs.

[1]: https://github.com/ForbesLindesay/redux-optimist

[ Parent | on HN ]