Automatic normalization requires the root query to match the structure of the response. Can anyone with a good understanding of compassus point of where the actual root query is swapped out for the 'route query' for the purposes of normalization? https://github.com/compassus/compassus/blob/master/src/main/compassus/core.cljc

@danielstockton https://github.com/compassus/compassus/blob/master/src/main/compassus/core.cljc#L365

Thanks!

This looks like it does it when the app mounts. Is there somewhere else that does this when merging from remote?

Referring to this part: https://github.com/omcljs/om/blob/master/src/main/om/next.cljc#L2336

I tried doing a tree->db in merge, but i ended up with just the lookup table of idents (lost the actual data)

looks like you want to use compassus-merge as your merge function, perhaps?

or you need to pass the query in to the callback in your send function

I'm actually trying to build the routing from scratch (using union query method like compassus) to understand the magic better. I think you're right though, I missed the multi-arity nature of send cb and the response is also keyed under the route. Thanks a lot, think I can progress from here.