I dunno. the reconciler docstring for :send says "The callback should take ... the query that was sent as the second argument"

tomjack: thank you, I try these hints out, I also think that referring to components from parsers/remote handling logic would be weird, but it also stands for a try

@anmonteiro is having a talk about om next on craft conf right now https://craft-conf.com/2016

it’s free online

There seems to be some sort of leak going on in Safari with om.next specifically. I haven’t figured out what exactly that causes it yet. Are there known problems with Safari?

@fifigyuri: when will we have the talk online ? I would love to watch it

it’s right now, showing demos, but it’s should come online, after the conference, the talks for last year are available, so this year should be too

nice, thanks

that’s the demo https://github.com/anmonteiro/craftconf-demo

wow, there are some great speakers there too

just missed anmonteiro's talk this morning 🙃

Hopefully they'll post it asap on youtube

hey all, i'm confused about how to introduce novelty from a remote. my app state is a list of items {:items/list [{:id 1, ...}]} and get normalized with [:item/by-id id]. i have a mutate function 'items/insert which simply returns :remote true. so, this works fine if i call (om/transact! this '[(items/insert {:title "foo"}) :items/list]) – the server parses and responds with the entire :items/list, and the frontend updates. what i'm confused about is: how do i set this up so the server only returns the new item, and the frontend merges that single item into :items/list?

in other words, in the remote, what should the :action function in ’items/insert return? and do i need to transform the response from (parser nil (req :body)) ?

If I have nested OM components (Next), Can I have queries for Subcomponents for keys not included in the parent component?

Basically, I am looking to have a Root “Widget” that has multiple subcomponents like navigation-bar, notification-bar. etc… But I want those to pull down their own state from the root reconciler. Or do I have to query the state at the Root component level and pass it down.

@dimiter: the root needs to compose every subquery

you can use (om/get-query NotificationBar)

Right, I saw that in one of the tutorials..

Just a touch concerned if I have too many remote reads on sub-components, will they trigger re-render at the root level?

hmm, i think so, but i think om implements shouldComponentUpdate so it should be performant still

(i’m not certain about this)

I will play around with it. I tried using shouldComponentUpdate at the root level and setting it to false, however that also prevents the sub-components from updating their props.

https://github.com/omcljs/om/blob/master/src/main/om/next.clj#L136-L148

What does this mean?

next.cljs:1229 Uncaught #error {:message "No queries exist for component path (torcaui.components.app/App torcaui.components.landing/AutoCompleter)", :data {:type :om.next/no-queries}}

I am trying to create a nested component and update its search params.

Figured it out, Root component has to dynamically pull in the child’s query. This helped:

https://awkay.github.io/om-tutorial/#!/om_tutorial.E_UI_Queries_and_State