Fork me on GitHub

Hey, I'm working on a #fulcro / #pathom version of realworld app My main propose it (re)learn and document/exemplification/best pratices of fulcro/pathom/eql applications Any kind of interactions(DM/PR/Solutions/doubts) are welcome 🙂


@souenzzo I would consider it a best practice to use RAD. Don’t have to use db adapters or even generated UI…but the attribute stuff and form/report logic handling is super nice for standing things up


In the "fulcro meetup" you said that "rad is developed for be easy to attach on a existing project" Which component do you recommend? Opened fulcro-rad-demo and I'm thinking about start with the login form


so, login is less refined, and I didn’t really mean it..the auth machine is the least refined part of the whole thing 😄


if I only had 3x as many hours in a day 😕


I’ll take a stab at making some intro videos…it’s about time I did that


the book is somewhat reasonable, but definitely out of date and not as useful as I’d want


I've been chewing over chapter 3 of the book for the past few days and find it quite enlightening :) would you recommend jumping straight to from there?


@U797MAJ8M You can definitely “make things” with RAD without a ton of know-how in Fulcro; however, RAD is meant to be a “stand it up quickly” thing that you escape from over time…you’ll need to really understand Fulcro to actually build anything real.


I think I'll continue to work through things the hard way then. thanks


Just understand that what RAD supplies (`defsc-form` and defsc-report) on the UI side are just macros that generate defsc. See the videos I posted


I'm on a wrong path? I'm still confuse if report will receive {:source-atronute [{:val 1] {:val 2}}} or directly {:val 1}


the generated UI doesn’t hurt for early stuff as well


and the routing is more fully baked


component options is just the right thing to do for generalizing certain things as well (hanging custom options on components)