Clojurians
#om-next
<
2017-01-09
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

joseph10:01:35

Hi, I'm using om/next to develop a frontend project, and there is always a question in my head when I read the om/next tutorial and wrote my own project, that is when the read-fn function in parser should take care of the query in the component, f.k.s: in the [Components, Identity & Normalization](https://github.com/omcljs/om/wiki/Components%2C-Identity-%26-Normalization) example, only the query :list/one and :list/two are handled, while those like name, points in the query of Person not, so what's the rule of query-handling, only those in the root query?

mavbozo13:01:42

@joseph in that sample app, since (get-person) already returns the attribute Person component need then read :list/one and read :list/two are enough

joseph16:01:20

@mavbozo thx for your reply

sova21:01:06

Is there a decent resource for going from (atom app-state) to integrating a datomic transactor?

sova21:01:14

That's my biggest hurdle at the moment.