Calling om/update-state! on some child of parameterized list component changes props the child receives to root props, I don’t know what’s happening. I’m out of my depth here, but testing this problem with example in om.next tutorial resulted in the same erroneous (I think) behavior so I reported the bug. Is it a bug or am I missing something? https://github.com/omcljs/om/issues/830

Are there any open source non trivial web apps using om.next out there?

the circleci frontend has bits and pieces https://github.com/circleci/frontend/blob/master/src-cljs/frontend/parser.cljs

I’m using om alpha 47, and it looks like I can get the component associated with a query directly through the ast using the :component key. But in some of the om.next source, it looks like it is taking the component information from the :query key metadata. Is there any reason I should use one of these over the other in my own code?