Is there a way to have a UI component inlined in its parent but still have a query that works well with fulcro's normalization? For example, when Person in PersonList is trivial (e.g., just a simple div), I don't want to create a defsc just for that and would like to simply write (for [{:keys [id name]} person-list] (div {:key id} name)) in PersonList.

But if I do that, how should I write the query for PersonList?

@zhuxun2 there is "create a component just for queries" in docs.

@souenzzo Thanks. I am aware of ui-less components, but that doesn't seem to be what I'm looking for. If I had to write a defsc with ident and query, which is going to feed to UI anyways, I might as well make a defsc with UI...

In other words, I'm looking for a shorter inlined syntax for normalization hinting, if that makes sense ...

I mean, an ui-less defsc is already very short to begin with... I use one for a filtering functionality in our product. I use that very same normalized data both for filtering and in another defsc for rendering the results

@zilti I see your point. Thanks. BTW that's what I am doing right now and I was just unsure if I missed anything else.

Are the remote mutations deduped on the server? I just made an experiment where I did (comp/transact! this [(my-mutation) (my-mutation)]), but judging from logs my-mutation only got run once on the server

On the client it did run twice though... why is that?

I believe that is currently not supported. I think the reason is that you can just make a new mutation that handles the logic of both

*the logic of running the mutation twice

I think that it's because both are sent in the same transaction and <something> :)