Clojurians
#om-next
<
2017-01-10
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

mavbozo05:01:23

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

jwkoelewijn13:01:54

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?

sova17:01:29

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

viebel19:01:49

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

viebel19:01:52

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

viebel19:01:11

Without having react re-rendering the component

sova19:01:43

@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

viebel19:01:24

What about unmounting the component?

viebel20:01:59

There is ReactDOM.unmountComponentAtNode

viebel20:01:12

Is it safe to use it inside om.next?

sova20:01:25

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