you mean the ones the plugin normally renders? You could look at the source of the plugin and see what it does.

Otherwise, look at the state machine definition source, and see what events are available, and trigger events that do what you want

Your computed props (third arg of component) has a bunch of useful stuff

I have update the example code. I just wish to row-actions. Wondering if there is an easier way to do it.

Also is there a way to render nested Form with same structure as a parent:

(defsc-form TForm [this props]
  {fo/id block/id
   fo/title "Blocks"
   fo/attributes [block/identifier block/context block/type
                  block/properties block/children]
   fo/route-prefix "block"
   fo/subforms {:block/properties {fo/ui property/Form}}})

(defsc-form Form [this props]
  {fo/id block/id
   fo/title "Blocks"
   fo/attributes [block/identifier block/context block/type
                  block/properties block/children]
   fo/route-prefix "block"
   fo/subforms {:block/properties {fo/ui property/Form}
                :block/children {fo/ui TForm}}})

Of course it is possible, but it isn't something that RAD supports out of the box.

I thought maybe it's the use of clojure.string, so I removed all references to that. Didn't help.

Weird.. restarted everything and it seems to work now.

your example isn't clear to me...circles in queries are not really possible without declaring alternate classes, since the call to get-query would be infinitely recursive. Is the data actually a circle in the database graph?

Recursive queries get you through most of those, but if the separation of top and bottom is more than one apart, then you've got a challenge.

if you put more exposition with your example and explain what you are trying to actually do (instead of me having to infer it from your code) then it would be easier to help

@tony.kay sorry to bother but do you have any tips for how to troubleshoot this? 🙏

Check the requires and make sure you didn't get F2 stuff 😛

make sure you're using my fork of devcards

your shadow aliases do not include that stuff

so your deps is either wrong, or your shadow-cljs aliases are

but I would expect a compile error...

oh, I see, you're running shadow from deps...that's why your classpath "works"

It runs and the workspaces shows

I am running clj -M:serve-puzzles which has dependency on workspaces

Ah I see what you are saying, I forgot about shadow-cljs.edn and its :deps {:aliases []} Not sure how it plays here. Maybe it does not matter the way I am running it, from deps?

doesn't...so

I see it start

Inspect button works

card is blank

Ok, you are luckier than me if Inspect works for you 🙂 Any idea why the card would be blank?

ah, inspector works now for me too, after some reloads (and I have also added :serve-puzzles to shadow's aliases)

I added :ui/red? false to initial state

and now it renders

I think perhaps the generated root checks to see that the props contain something to avoid errors

and your props were empty

Ah, thanks a lot! I did not even think about that possibility. You saved me 🙂

yeah, rendering empty props can cause crashes in components that don't expect it, so I think that was the reasoning on the generated root

if you had not used wrap-root? you would not have been confused. Generated code is sometimes "too" helpful 🙂

do you know where is the generated root defined?

just jump into the source of that helper

found it, thx!

yeah, line 62

(if (seq root) ...

what about me sending a PR that adds an else branch displaying some helpful error message?

ok by me

Like this, @tony.kay ?

https://github.com/awkay/workspaces/pull/5

I don't think it needs to say "WARNING"...just something like "Your top-level component cannot be rendered because the props for it are nil or empty. Please make sure you included a non-empty initial state in that component"

PR updated

Remember that first and foremost RAD is about patterns not artifacts. The fact that I've supplied a report artifact is a convenience, and one in which I am not planning to ever cover every possible use-case. Doing so is folly IMO. Instead, everything has an escape hatch. When you get to cases like this you need to take more control of the overrides of core bits of that artifact (which it is designed to allow). Specifically, what you are asking for requires that you override and tune the state machine, and add whatever custom options you need it to support.

Basically, as soon as you go beyond the basic case, you have to take more and more control. Fortunately, the patterns establish ways where you can easily reuse those advancements throughout your app

Often, you can work through some of these cases by being a little inventive within the model itself: Comments need not be resolved by a report at all...so why are you asking it to to begin with?

the report only loads what you tell it to load. Don't include the column in question?

We want to show the comments but for performance reasons we want to load them async/lazily and only for the currently visible page. It is essentially just a perf. optimization.

yes, and if that is what you want you must customize the state machine to do a more complex thing than it currently knows how to do

• Add an option to the report that supports the concept (some field is not loaded by default, update state machine to look for that and use it in :without) • Add an event that does the proper thing, or augment one (modify the "next page" stuff to trigger focused loads for just the rows that are appearing)

Thank you very much! I thought of a number of workarounds but not about this optimal approach 🙂

Eventually it would be nice to have some "beefed up" state machine definitions in a library ppl could choose from.

but the state machine is just a map, so it's pretty easy to augment one without copying source...just assoc against the existing one

That sounds simple enough, thank you!