I think I'm missing the theory behind :keys in the merge result. The default-merge causes the entire root component to queue, correct?

It seems to me that any good merge implementation would have to, since new data may require new components to be rendered.

It's not enough to find components which need to be queued if some of the components which need queuing may not exist yet.

@anmonteiro do you have anything good to read on how Compassus handles idents in components wrapped in a mixin?

so if I have a route and a component associated, and that component has a query with Ident, when the novelty comes back from server, it suppose to normalize data based on the Ident, right?

when novelty comes back from server and there’s a query in the root component that has Ident somewhere that data should be normalized automatically, right? you don’t have to have any custom merge fn or whatever?

I just tried with a simple om app, and it does normalize automatically when novelty comes from the back-end, if there’s a query with ident.

I can’t find a way to make Compassus respect idents though

Ok, I have figured it out… apparently this

the last sentence is quite important…

Om by default works without the second argument - Compassus needs query to be passed in that callback, otherwise Idents down the tree will be ignored and normalization won’t happen