om

Please ask the channel first, not @dnolen directly!
2018-04-29T19:26:12.000073Z

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

2018-04-29T19:26:56.000101Z

Thanks!

2018-04-29T19:28:28.000104Z

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

2018-04-29T19:32:19.000106Z

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

2018-04-29T19:33:26.000053Z

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

anmonteiro 2018-04-29T19:35:01.000005Z

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

anmonteiro 2018-04-29T19:36:21.000066Z

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

2018-04-29T19:37:45.000051Z

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.