Does anyone have an example of Fulcro with Crux ?

Has anyone added general undo support for fulcro? I imagine you'd do something like this (https://swannodette.github.io/2013/12/31/time-travel/) and store the history vector on the fulcro app, but I wonder if there are any code samples for fulcro to look at

for now I'd like a simple undo stack - no fancy redo/tree undo

I am also thinking about how you'd have some domain actions that are composed of a few mutations, so "undo" would have to potentially traverse back into the undo history a few entries

@danvingo F2 had this built-in, but no one used it so I dropped it in 3. It’s simple enough with the new pluggable tx system to add it back…or for that matter you could add wrapper function around transact itself that could capture that history. Navigating to it is as simple as resetting the state atom and scheduling a render

Here are some other interesting things around this: What if you had checkpoints just before a full-stack operation (i.e. a form save) so that you could do an optimistic save (i.e. route away from the form immediately), but in error-action if the form returned an error you could clear the network queue (all other full-stack things would be behind that one) and time-travel them back to the last known good point. I started to implement that some time ago, but just didn’t…but time travel for full-stack error handling in an otherwise optimistic app is new direction to go in SPAs that I think is interesting.

Of course the support viewer concept is just a transit encoding of that history sent to a server for developers to use in reconstructing what was going on in the UI..in that case it is also nice to add in the history of tx’s as annotations on each history node

backtrack app state on error does sound pretty nice

implementing undo in general sounds hard though right? if an undo takes you back past the point of a full stack mutation i think you'd have to always ensure that you trigger an inverse mutation right

unless your server-side data store also somehow supports an undo operation

yea, was just thinking through why I thought up wanting this and realized the server is going to have to be involved for anything meaningful

specifically I was thinking of undoing an accidental deletion - that goes full stack

i feel like you'd have to do extra work to account for the fact that other clients might have done things that would make the true "inverse" even more complicated

if your db supports it one stupid way to implement it would be to rollback the entire db state but obviously other users might not appreciate that

not as easy as it was in desktop apps!

with crux it becomes possible to reset an entity, but it would still require thinking through relationships

is there any standard advice for code re-use among different handlers in a uism? i find i'm often having to repeat things like lets

does fulcro support render-as-you-fetch like react with suspense? https://reactjs.org/docs/concurrent-mode-suspense.html

@kevin842 fulcro never used "fetch-on-render" or "fetch-then-render" I'm not sure if we can call "render as you fetch" in fulcro, it's more like "know what you fetch. always render" (?!) On Scaling Full-Stack Applications - Wilker Lucio da Silva presentation, wilker talked about some EQL/pathom integration that allows partial responses for EQL queries.