om

Please ask the channel first, not @dnolen directly!
tianshu 2017-12-26T01:59:02.000090Z

Yes, this help me. But something still not clear to me, if I have component A, B. B is rendered in A, and use a global singleton state {:app/x 0}. If I B has a query [:app/x] and A has query (om/get-query B), when I call (om/tansact! this-b ...) it will say has on query on this path. so I have to transact! with reconciler, is it correct?

2017-12-26T06:09:21.000118Z

@ho0man shared a file: https://clojurians.slack.com/files/U6CE37RK6/F8JDDV5L0/plotting_using_echarts_and_om.txt and commented: Hi, I'm just starting to use cljs and om next. I am trying to use a js charting library echartsjs through cljsjs This snippet gets a TypeError: dom.getAttribute is not a function on line

tianshu 2017-12-26T09:26:33.000064Z

not sure if this is relevant, the props in '(dom/div {:height 400 :width 500} "holder")' should has a tag #js.

2017-12-26T10:43:18.000064Z

Thanks,

2017-12-26T10:43:28.000053Z

yeah you're correct

2017-12-26T10:44:14.000121Z

But the error I get seems to be related to some difference between js dom object and om.nexts', I think

dirklectisch 2017-12-26T21:57:01.000061Z

Any good examples of recursive om.next parsers around that incorporate remote sync?