This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-05
Channels
- # announcements (1)
- # asami (25)
- # babashka (78)
- # beginners (24)
- # clojure (15)
- # clojure-europe (21)
- # clojure-losangeles (4)
- # clojure-nl (1)
- # clojure-norway (13)
- # clojure-uk (11)
- # cursive (17)
- # datomic (29)
- # events (1)
- # fulcro (4)
- # hyperfiddle (6)
- # jobs (1)
- # lsp (20)
- # malli (9)
- # off-topic (7)
- # pedestal (1)
- # polylith (2)
- # practicalli (1)
- # rdf (7)
- # reitit (1)
- # remote-jobs (1)
- # spacemacs (17)
- # specter (24)
- # vim (1)
I'm curious if people tend to use nubank/workspaces? Or is there a better way to build up components/interfaces. I'm just starting building real apps in fulcro and trying to get a feel for an effective workflow. I'm planning a datomic/pathom backend. Any workflow tips would be welcome! Do people use devcards/workspaces, or build in-place merging sample data into the client DB? Does anyone have a workflow they feel is particularly quick/effective for building up interfaces? For now I'm using fulcro without the RAD library, while I get used to it.
My applications are sufficiently complex to warrant UI tests, so I just try things with mock data as I develop them. However, if I had a component with multiple state or such. I’d certainly look into workspaces.
Thanks @U0522TWDA! So do you make use of merge-component
to get data into the client DB? Or do you tend to just work on the whole application all at once and not bother with building component-by-component?
It depends 🙂 Mostly, I did what fulcro-rad-demo does and insert some data into the DB and use that.