fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
Björn Ebbinghaus 2020-11-27T00:09:41.321700Z

It may be out of date. But you could look at this project: https://github.com/hhucn/decide

Jakub Holý 2020-11-27T15:17:54.322Z

Can the ok-action see the mutation params? Then you could (if :redirect? (transact!...))

Jakub Holý 2020-11-27T15:20:40.322200Z

I guess the result the action sees might also include the original transaction o you could look there?

cjmurphy 2020-11-27T15:38:15.322400Z

I would argue that having mutations with descriptive names results in more maintainable code than mucking around with parameters does.

1👍
genekim 2020-11-27T22:05:12.002Z

Thank you! Makes total sense now! And PS: just watched your RAD video on YouTube, after listening to your interviews on ClojureScript podcast and scanning all the docs. Wow. I'm inspired to give it a try this weekend!

genekim 2020-11-27T22:06:16.003500Z

Thanks for all your great work — Fulcro RAD seems like the closest we've come to Microsoft Access for designing form based apps. That's meant as a huge compliment!!! Keep up all your amazing work!

Jakub Holý 2020-11-27T23:22:28.003800Z

BTW I believe I remember reading in the book about passing info about UI-only concerns through a (remote) mutation so that they could be used in ok-action. Try to have a look there. Sadly, I don't remember any details.

Björn Ebbinghaus 2020-11-27T23:50:34.004Z

Can I ask you both how you deal with such sitations? @cjmurphy @holyjak Do you just write a new mutation for each button or whatever in your application?