:key

oops sorry

i just upgraded to react 1.5 and now I'm getting "react.inc.js:19500 Warning: flattenChildren(...): Encountered two children with the same key, 2:$undefined. Child keys must be unique; when two children share a key, only the first child will be used."

@octo221: you need to set react-key on the factory you’re calling

yeh got it, provide {:key :key}

to (build-all

oh you’re using Om Now

old Om yes

is there a guide somewhere to how to upgrade to Om Next and what's changed ?

@octo221: its very very different, best to start with some of the talks david nolen gave about it

@isak: is there nothing written about it ? I prefer text it's faster

@octo221: well there is this: https://github.com/omcljs/om/wiki/Quick-Start-(om.next)

also a tutorial here: https://github.com/awkay/om-tutorial

cheers...is Om Next relatively stable to use ?

@octo221: there’s a blog series i recently started on building a mobile game using Om.next: https://medium.com/@markfayngersh/connect-lets-build-a-game-37620df1ddf7#.3uh4kt71c

there’s a repo to go along, but i’m also striving for grokable text

Has anyone written anything about best practices for query keys?

Like, how best to model your data as a queryable graph?

@peeja I would be interested in that - been trial and error to figure how to make ui trees with proper query/path/ident

om/process-roots doesn't seem to support recursive queries. Specifically, move-roots assumes join map values will be a seq. Is this a known issue? I don't see an issue for this.

@cmcfarlen: process-roots also does not support unions. I recommend not using it and writing your own custom version for that use case so you have more flexibility around how queries are re-written.

@noonian: I read through the issues with unions. I think this is a simpler issue. If the join is recursive, then there aren't going to be further roots to migrate and move-roots can just return the accumulated results.