With fulcro-template, I am getting an exception in app.model.session, the compiler says java.lang.RuntimeException: Invalid token: ::m/returning

I also have to say that I updated the dependencies in deps.edn, so I guess something changed in Fulcro?

you sure the alias m is namespaced?

could be in a comment

clj(s) won’t compile a comment that uses an alias if the alias is removed from the requires

(comment ::m/a) and #_:this-kind)

things that follow ; are completely ignored

Just published a post about implementing client-side routing in fulcro at https://chrisodonnell.dev/posts/giftlist/routing/. I haven't blogged before and wouldn't consider myself a fulcro expert; I'm happy to hear any constructive feedback.

In RAD, how do I fetch the initial data for a report? I have assumed that with ::report/run-on-mount? true it would run the query automatically but it isn't the case, the report shows empty. Do I need to df/load! manually, as with standard Fulcro? How? Thank you! When I run (df/load! app :kostnadsdeling/all-organizations ui/OrgList), the report will show the data but it does not look correct in the DB - the root key :kostnadsdeling/all-organizations is a vector of many [:component/id :OrgList] . I wanted it to be what in practice is under :tem-organization/organization-number, i.e. ["org1" {:tem-organization/organization-number "org1"},..]. The LOADed query is

[{:kostnadsdeling/all-organizations
  [{:kostnadsdeling/all-organizations ;; twice ?!
    [:tem-organization/organization-number
     :tem-organization/organization-number]}
   [:ui.fulcro.client.data-fetch.load-markers/by-id _]]}]

(defattr all-organizations :kostnadsdeling/all-organizations :ref
  {::attr/target    :tem-organization/organization-number
   ::pc/output      [{:kostnadsdeling/all-organizations [:tem-organization/organization-number]}]
   ::pc/resolve     (fn [{:keys [query-params] :as env} _]
                      #?(:clj
                         {:kostnadsdeling/all-organizations (queries/get-all-ksd-organizations env query-params)}))})

@holyjak It does auto run with that option. Sure you have data?

look in inspect

you should not use load!…you can trigger a refresh from UI in the report with (`report/reload! reportinstance)`

Use inspect to verify that your network request is sending the right query, and that you’re repsonding with right value

NOTE: on current SNAPSHOT I’m actively working on report

and I’ve renamed a few more things 😜

I’ll push an update shortly…just polishing it off

added a bunch of cool stuff

I looked in inspect - network and the only request there is

[{(com.example.model.account/check-session)
  [:com.fulcrologic.rad.authorization/provider
   :com.fulcrologic.rad.authorization/status 
   * 
   :tempids]}]

(report/reload!
   (comp/class->any com.example.client/app OrgList))

ok, RAD demo pushed, along with new snapshot versions of libs. • ::report/edit-form became ::report/form-links (see demo). Allows you to create links to many diff things on a single row. NOTE, this works by leveraging a resolver that can give the correct ids from the back end . In the demo case (invoice list) the :account/id has a resolver on an :invoice/id input. This allows the report to automatically get both IDs for each row. See https://github.com/fulcrologic/fulcro-rad-demo/blob/develop/src/shared/com/example/model/invoice.cljc#L50 • ::report/column-key was the wrong name, renamed to ::report/row-pk • Added ::report/actions and ::report/row-actions. See demo. • ::report/BodyItem is no longer needed in reports, unless you want to custom render, but then it simply needs query/ident, NO report params • ::report/row-style and ::report/layout-style now exist for choosing (or plugging in) custom report layouts and row renderers. See demo. Predefined values for these are :list and :table. If you use :list, then only (up to) two columns are supported. • MANY of the keys in things now accept either scalars or functions. I still need to make the parameters consistent. This allows for things like easy i18n, computed labels, etc.

@holyjak No, you cannot use a report CLASS, it must be a report instance…and you should probably not be calling it unless you’re writing a custom renderer (it must be called from such a renderer, since that’s where you’ll get the on-screen instance)

Reports start when they are routed to. Make a landing page, then route to the report.

I don’t have a hook for you to start with a report on screen at app load

See report.cljc…this line:

(uism/begin! app report-machine report-ident {:actor/report report-class}
          {:route-params route-params})

that’s what you do to start a report

(route params can be empty in this case)

so:

(uism/begin! app report/report-machine [:component/id :OrgList] {:actor/report OrgList})

should work

I’ll make a helper function

snapshot pushed with helper: (report/start-report! app OrgList)

I wish I had time to make more videos…alas, have to work and pay the bills 😞