fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
tony.kay 2021-04-18T02:16:36.143600Z

Hey, thanks for playing with the new stuff and finding issues! I had not had time yet to test various composition scenarios, so I’m glad someone’s helping out. It’s an interesting problem, and a “lovely” solution. I love the function name. Encourages so much confidence 😜 So, yeah, I can’t tie things to React DOM there. We can instead create an optional batch-updates parameter on the app that can be installed by the creator of the app, which defaults to a no-op. The down-side is then everyone has to remember to install it, or we have to make different base nses for each target (native-app, dom-app, etc.). No “free lunch” in building this kind of stuff. The primitives look so lovely on the surface, then you try to compose them and crap breaks.

tony.kay 2021-04-18T02:17:48.143800Z

I guess there could be a global var for that, and requiring dom could side-effect and install it 😕

tony.kay 2021-04-18T02:19:19.144Z

I’ve been a bit worried about this general composition problem since I started playing with these things in the context of hooks and arbitrary state composition. It makes me think Fulcro already has it right having you compose most things from root, and then using things like this at the leaves.