Does Fulcro/Transit not support BigDecimals? When I send 123Mfrom a Pathom resolver, the Inspect - Query view shows the value as #object[UX [TaggedValue: f, 123]] Or is this OK and will work just fine in the UI?

Reading the RAD book's docs for ::report/source-attribute, it seems that the data must be under a top-level key in the DB, right? So I cannot have a list (report) invoices with the action "show invoice rows" that would show another report with the invoice's details, without loading them into a top-level key first? Actually I have a standard defsc for LatestInvoice and would like to have it display also an on-demand list of the invoice rows. But it is the same problem - I have a parent component that has the data and wants to display them in a report but has to put them under a top key first.

BTW, since I already have all the attributes defined, it would be nice to be able to leverage them also for a single-entity display, ie say this component should display these attributes of account, in the given order, using the default layout (likely a table)

Regarding ::attr/identity? - what if the DB table has a composed primary key, i.e. it is formed by 2+ columns and there is no single-column id? I guess so far out of scope?

Hi all - I’m exploring the fulcro-rad-demo and compilation with shadow-cljs watch main fails with a Use of undeclared Var com.fulcrologic.rad.application/install-ui-controls! error. Any idea what I’m doing wrong? Submitted a bug here: https://github.com/fulcrologic/fulcro-rad-demo/issues/7

I am trying but failing to find out how to use a Report to show "rows" of a selected item. I have a list (report, actually) of invoices with a "Details" button. When the button is pressed, I want to somehow load rows for the selected invoice and show them in a report. Reports work fine when the data is at the top level of the DB / there is a pathom resolver for its ::report/source-attribute but using to show the details of a selected entity escapes me...

To all and @alex-eberts make sure if you try out RAD demo that you use the master branch. develop is in flux and uses snapshot versions that I sometimes forget to publish. I did a bunch of cleanup and normalization yesterday, including moving some things around and renaming some keys. I’ll change the default in GH so no one else makes that mistake. Contributors to the demo should branch FROM develop. Master is always a stable release (if I do things right)

I can run a mutation (both server and broswer -side), and see the network request and response in Fulcro Inspect -> Network. Everything works. However, when I use "Send to query" to send the request to Fulcro Inspect -> Query, and then run the query. The response is:

{fulcro-app.db.mutations/update-team!
 {:com.wsscode.pathom.core/reader-error
  "Mutation not found - {:mutation fulcro-app.db.mutations/update-team!}"}}

I'm struggling to get a list of data in a component one level down the tree from root. Here's my example:

(defsc Person [this {name :person/name id :person/id}]
  {:query [:person/name :person/id]
   :ident :person/id}
  (dom/div (dom/p "Name: " name)))

(defsc People [this {:keys [all-people]}]
  {:query [ {:all-people (comp/get-query Person)}]}
  (dom/div "HI all people"))

(def ui-people (comp/factory People))

(defsc Root [this {:keys [list-component all-people]}]
  {:query [{:list-component (comp/get-query People)}
           {:all-people (comp/get-query Person)}]
   :componentDidMount (fn [this] (df/load! this :all-people Person))}
  (println "list-component: " list-component) ; <- this is nil
  (println "all-people: " all-people)         ; <- this has data
  (dom/div (ui-people list-component)))

;; After network load, db has:
;; :all-people [[ :person/id #uuid "a097e870-2a91-4497-ae0d-72f7e178c7f1" ]]
;; :person/id {#uuid "a097e870-2a91-4497-ae0d-72f7e178c7f1"  {:person/name "test" :person/id #uuid "a097e870-2a91-4497-ae0d-72f7e178c7f1" }}

@danvingo add :target [:list-component] to your load

ah thank you!

I have a workspaces card that shows a form, but I don’t know where to put my add-form-config

@roklenarcic not sure what you mean

you could put it in initial state

(fs/add-form-config Cls (get-initial-state Cls {}))

I think that’s what you’re asking

there is a tree version and a normalized version of that function. The tree version is for cases where you ahve a tree of data, like in initial state

add form config expects to get the root tree, right?

because in workspaces the component of the card is not at root

@roklenarcic You can ask ws to either make a mock root for you, or trust you on the root. add-form-config expects the tree of the form itself.

so, you could make your own root so you can wrap the get initial state…I don’t remember if ws has an option for specifying initial state…I mean, you could pass app options to the card if you’re embedding an app and set initial state manually.

I usually just write the root in these cases so I’m in control

you could also do it as a mutation in the app-did-mount thingy

hm OK, I will try it, I got a weird state when I did (fs/add-form-config Cls (comp/get-initial-state Cls…. , so I thought it needed to be root, will investigate further

yeah I was using wrong add-form-config