om-next

mavbozo 2017-01-10T05:43:23.000208Z

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

jwkoelewijn 2017-01-10T13:33:54.000210Z

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)
I get a failed assertion
(or (satisfies? p/IReactComponent x) (satisfies? p/IReactDOMElement x))
, is this a known problem? or am I (most probably), doing something wrong?

sova-soars-the-sora 2017-01-10T17:23:29.000211Z

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

Yehonathan Sharvit 2017-01-10T19:53:49.000212Z

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

Yehonathan Sharvit 2017-01-10T19:54:52.000213Z

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

Yehonathan Sharvit 2017-01-10T19:55:11.000214Z

Without having react re-rendering the component

sova-soars-the-sora 2017-01-10T19:56:43.000215Z

@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

Yehonathan Sharvit 2017-01-10T19:57:24.000216Z

What about unmounting the component?

Yehonathan Sharvit 2017-01-10T20:15:59.000217Z

There is ReactDOM.unmountComponentAtNode

Yehonathan Sharvit 2017-01-10T20:16:12.000218Z

Is it safe to use it inside om.next?

sova-soars-the-sora 2017-01-10T20:19:25.000219Z

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