What is the best way to get a react-ref into a component created with a factory? I currently merge it into the properties given to the factory, but this feels like a hack.

Is there a way to pass non-app-state data to the root component similar to how we can from a parent to a child with (om/computed child-factory {:some :data})? I tried (om/add-root! (om/computed reconciler {:some :data}) App (gdom/getElement "app"))) but it didn't work.

Why would you want to do that? Can't you get it into the state by using transact on the reconciler and then ask for it in the root?

In order to interact with some stateful services that are already created before the UI tree is. I realize again that should only be done through the read/mutate handlers.

@thosmos there’s no way to do that beyond :shared which is once only.

Can anyone explain what exactly is the difference between Datomic Free and Datomic Pro? Especially in the context of Om? Can I still work normally even if I used the Free edition?

hi guys, what is the best practice to change local-state of nested component. For example in the accordion-test sub-component, how can I change make the current one to be active. https://gist.github.com/rhacker/2505dcff4f53c4b9ceeb

is om/set-state! still the right one to use in om next ?

@nxqd: Yes, see https://github.com/omcljs/om/wiki/Documentation-%28om.next%29. If you work with nested components, you can pass callbacks down using om/computed.

@kauko: you should be able to do everything basic using datomic free

just remember to use the "free" transactor instead of "dev" when you want to persist things on disk

Thanks! So, what exactly are the reasons people would want to switch to Pro from Free? I'm looking at the pricing page, but I don't really understand how the differences of the two versions would affect me - I mean, why would I need "SQL Storage" for example?

@kauko: you should have low perf expectations for transactor local storage. Also I don’t believe you can integrate Free into a commercial deployment?

I often see warnings like Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of prodnet$ui$login_manager$LoginManager. ... yet the component mentioned here is a singleton child of the root component.

Can anyone tell me something about that?

@smeister: not without showing some actual code

That's it: https://gist.github.com/SMeister/d6d0c03c4edf72441a24

@smeister: it might be because you are using sablono

or hiccup (or whatever that is)

it's sablono

so not an Om problem

@smeister: thanks 😄

@dnolen: Thanks, :shared is perfect. I only need it one time.