Fork me on GitHub

Hi, I’m having trouble understanding how Fulcro child components and mutations work with nubank workspaces. I have a fulcro3 card and it has a stateful component as root (same as in the fulcro template). In the root component I can set-value! as you’d expect, but in child components I get DEBUG [com.fulcrologic.fulcro.algorithms.tx-processing:694] - Scheduling a render and nothing else. Are you supposed to have just a single stateful component per card?


i'm struggling with being confident in optimistic updates--let's say i have a [:foo/id :bar] that has a property :message, and that in my UI I have a checkbox that emits (set-message {:ident [:foo/id :bar] :value "VALUE"}). now, if two users concurrently edit :message, it's easy to arrive in a state where A thinks :message is "A" but B thinks :message is "B" and the server has chosen whichever one came later as the truth. the way i see it i can only think of two reasonable responses: 1. accept that clients can see "wrong" information sometimes (which might be ok if these situations are rare and/or inconsequential) 2. come up with a way of syncing clients with the db's truth (e.g. returning the entity's full value as a result of a mutation) (2) might very well be OK--it might make network traffic a little higher than it needs to be but it ensures consistency. as for (1), there are some areas of my app where i'm not prepared to say inconsistencies aren't a big deal. am i missing something here?

Tyler Nisonoff23:08:31

Anyone have a good understanding of RAD form rendering? I'm trying to create a form that involves a tuple attribute, but getting "No renderer installed to support attribute" Having trouble figuring out where in the RAD code renderers are created for various attribute types / if theres a way to define a custom renderer for an attribute used in a defsc-form

Mr. Savy23:08:56

I have returned after months of absence only to find that fulcro-garden-css is hard to understand. no matter the struggle, I persist regardless!