@tony.kay a list of list items, they have a same dropdown ui component wtih same dropdown's options, I want to know which is a better way to define the :query in defsc list-item to normalize db. Now, I just pass a parent(list)-computed data (dropdown's options) to children (list-items) by using prim/computed, so I just need normalize the data of the options once in Root (list).

You could look at the dropdown examples in demos

or the implementatoin in bootstrap3 namespace

https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/ui/bootstrap3.cljc#L491

http://book.fulcrologic.com/#_cascading_dropdowns

The query for a component is always just the data it needs…e.g. :item/id, :item/value, :item/label

the ident can be based on the id

OR, since the value has to be unique, that could be that ID if you don’t have one

once it has an ident, you have normalization

@tony.kay Thanks,

need help,

How to make the Dropdown's search work. I try {:search (clj->js (fn [] ...))}, but don't work.

the behavior just like {:search true}

Forget it.

Just need to reload page.

Anything against giving the HTML body tag an id and use it as app root?

Appears to work fine (tried it in fulcro-template).

@maridonkers the problem with setting your entire body as the app is that in case anything adds something to your body (like developer tools or any kind of plugin you want) it will break the react tree since you are changing elements out of it's control, so I would recommend don't doing it, is there any limitation you are having using the internal element?

@wilkerlucio Thanks, won't go that way (app on body tag). Rationale was Bulma instructions on section reading "Use sections as direct children of body." But that doesn't seem an actual limitation so I'll use a div for app.

how does df/lazily-loaded and its :ui/fetch-state property on entities relate to network loading markers?