@currentoor Thanks for the in depth example. Both yours and the books examples seem to have the idents backwards, to my beginner’s eye. :tab is constant, the front bit seems to be the id, so I’d want to do [:TABS/by-id :ucv.ui.foo], to keep the tab definitions go inside a tidy table. Is the point of this to leave open to extension a different type of view than :tab for each ui component?

@sooheon you’re welcome

so the problem with what you’re saying > to keep the tab definitions go inside a tidy table is this means all the tabs need to be similar, since they are all in the same table and they would need to all have a similar query structure

but they are very different, some have sub-routers, some have other sub-components

typically they are very different

Ah, that’s right!

that said, if you look at your app-state in the inspector, or the DB view in the book, you’ll see all these tab idents are neatly placed inside the router’s table

Weird though, I think my app has a :COMPONENT/by-id table with components that have very different shapes

:fulcro.client.routing/routing-tree

not sure how that’s currently working

in you app are actually calling it :COMPONENT/by-id?

I guess that only works while the initial-state is provided per component, but would break down with loads based on component class?

yeah

it should be something more specific like :account/by-id and :person/by-id

i’m guessing you’ve used SQL databases before right?

it’s just like that, you want to store separate models in separate tables

rather than have one giant table for all your schema

think of :account/by-id as the name of a table

in fact you could totally called it :accounts or :account/table

mhm.. I still need to adjust from nested-hashmaps thinking => normalized db

normalized db is the default DB, like SQL, that everyone uses on the backend all the time without batting an eye

except people aren’t used to using it on the frontend 😅

yeah, the ease of hashmaps just hooked a lot of people, I think

even though it has a lot of the same benefits

yeah exactly they’re easy, until you have more than one view of some piece of data

then you have to do backflips to keep your data consistent

@currentoor @sooheon So, the ident order. I regularly use :COMPONENT/by-id for singleton components, and @sooheon you are right the router ones “look” backwards. I’d prefer they all go in the same table as well if they are singletons, but unfortunately the real issue has to do with union queries. The router component in Fulcro is more about optimization that routing to be honest. You want a union query to ensure the query stays fast, but unions SWITCH on the FIRST component of the ident..thus, THAT is the part that has to vary,

If you want more details on this, watch this video: https://www.youtube.com/watch?v=HJBI24yAdBQ&t=612s&index=12&list=PLVi9lDx-4C_Rwb8LUwW4AdjAu-39PHgEE

which is where I show you how that router is basically derived

ah no wonder I didn’t get this, I haven’t understood unions yet

hmm interesting, i always thought of tables as database tables, but yeah i suppose you could put all singletons in one table

yeah, the routers work the way they do to optimize the query…and that is the primary reason I added defrouter…it is the most optimal way to switch UI while optimizing query overhead

either that or dynamic queries (which would support it the other way around), but the Om Next code (when we were using Om Next) for dynamic queries isn’t quite fully fleshed out. I’ve since fixed that in Fulcro, but dynamic queries are relatively untested compared to the rest of the system.

https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/websockets/components/channel_server.clj#L17-L19 this looks like it prevents having several component instances

Just curious: anyone using fulcro with a yada backend?

Hi, coming back to cljs after a long hiatus. Getting to know fulcro. (I've used om.next a little when it was starting). Trying to understand the fulcro template. One question: What is the benefit of shadow-cljs.edn integration with leininingen since the :cljs config there is so small ?

@nha FYI there are two versions of websockets.

you’re looking at the old one

https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/websockets.clj