Is it possible to cancel the remote side of a mutation, from within the client action? I’m thinking about a undo -button (which is more of a “prevent remote action & undo local action”), and where I would implement that.

The action always goes first….hm

I’ve never tried that though. See book on the code, but I think it might work

unless I’ve closed over something in the tx processing that makes it not 😜

http://book.fulcrologic.com/#_aborting_loads_and_mutations

and http://book.fulcrologic.com/#Abort

You could also make a local-only mutation that conditionally calls a diff mutation that does go remote. OR, you could put logic in the remote that changes if it returns true/false

you can use the state atom in env to look at the current state, and even see the historical value of state before action ran: http://book.fulcrologic.com/#_the_env

So I’d probably recommend the last approach @jakobssonrobin

The tx processing in f3 does those things in order (action, followed by remote(s))

@fjolne.yngling Releasing Fulcro 3.1.7 with the patch you need for native template

stand by…tests not all passing 😞 I had another patch that changed args on something. Fixing that first

@fjolne.yngling so, let me know when that last PR is ready/tested. I merge the others.

@tony.kay thanks, will add cookies support for native as soon as i get to the laptop