@sova you want om.next remote to communicate directly with datomic transactor?

Hi there, I’m playing with om.next and got completely excited about the prospect of server-side rendering of components, and even finding an example on @anmonteiro’s Github page, so I took this as a guideline, but whenever I call

(dom/render-to-str)

(or (satisfies? p/IReactComponent x) (satisfies? p/IReactDOMElement x))

@mavbozo na i am just wondering about setting up remotes... as simple as writing mutate/read fns that talk with datomic.api/q?

How could I make a om.next component render only once at init time and never render again after that?

I’d like somehow to leave the component in the DOM and modify it from outside react

Without having react re-rendering the component

@viebel my guess is that you can add the element to the page and not supply a react-ID somehow... although i'm uncertain of the behavior at that point

What about unmounting the component?

There is ReactDOM.unmountComponentAtNode

Is it safe to use it inside om.next?

Ummm.. probably! Optionally you can create a totally different root component and mount it onto another div in your app.