@eric.shao you're getting “name nil, mate nil” in the Person component because, as you can see in the PeopleWidget component, the data you're passing down are idents ie. [:db/id 1] instead of actual results eg. {:db/id 1, :person/name “bob”}. try checking the root query and make sure all sub queries have been properly composed using om/get-query to allow om to denormalize idents into data.

@ianchow thank you. If “idents” involved,then every component level should have IQuery [{:key (om/get-query child)}] ?

I thought PeopleWidget should not have query-expression.

Now my code is this:

They show! Another question: How to control the recursive-query ’s nesting level?”

@eric.shao check out section on recursive queries. writings by anmonteiro. https://anmonteiro.com/2016/01/om-next-query-syntax/ https://anmonteiro.com/2016/01/exploration-patterns-om-next-part-1/ https://anmonteiro.com/2016/01/exploration-patterns-om-next-part-2/

Thank you @ianchow 😀

Hello, is untangled designed to be used for universal apps (server side rendering in clojure) ?

@claudiu It is designed for full-stack SPAs. Server-side rendering for initial page loading speed is in progress (latest snapshot should do it, but not well tested, yet).

I don't know what you mean by "universal". If you mean you'd like to serve html pages on each mouse click via server-side render, then no...don't do that.

@tony.kay I meant server-side rendering for initial page load, also love the user experience without initial loading states. Thank you, will give the latest snapshot a go :)