Clojurians
#cljsrn
<
2015-12-07
>

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

adamfrey18:12:15

I’ve been building off of @nodename’s https://github.com/nodename/AwesomeProject repo and I’m running into a problem getting om.next working with Android react-native.

adamfrey18:12:55

is anyone else doing any work in this world (om.next + android RN) other than me and @nodename?

mfikes19:12:32

@adamfrey: Good question. Of the main approaches, Natal is iOS + Om Next, and Re-Natal is iOS / Android + Reagent. I don’t think I’ve seen Om Next on Android.

adamfrey19:12:41

I did forget that re-natal supported Android. I’ll go check that out.

johannjohann22:12:12

is anyone seeing mounted components losing their defui class info?

johannjohann22:12:26

i was having issues using 'set-query' on my root component and maintaining a reference to the root-class rather than its mounted counterpart seems to have solved it

johannjohann22:12:33

also was coming up when i was testing sends

johannjohann22:12:59

i am using ambly, and the bug shows up when i connect using piggieback or straight from the terminal (ive seen cljs discrepancies between these two setups before :'()

johannjohann22:12:08

i fixed the crappy formatting in my gist my b B-)

artemyarulin22:12:22

don’t know how to help, there are two reference projects that I know which works: one that I mentioned from mfikes and this one https://github.com/iamjarvo/zooborns

artemyarulin22:12:54

Maybe you can check how they work with RN

johannjohann22:12:27

yeah ive had a fine experience up to that point of fooling around in both projects, things just started to get weird when i tested sends and set-query etc

johannjohann22:12:11

ill try to get a nice minimal reproduction of the bugs for public consumption

artemyarulin22:12:25

could you check that it works in browsers? Maybe it’s om bug

artemyarulin22:12:42

yeah, min case would help a lot

johannjohann22:12:53

i have a hunch that theres a discrpenancy in how instantiated components behave in rn v react

johannjohann22:12:58

the logic branching to handle "eliding" probably needs to be extended for the rn case or something. but also it could be like a silly typo somewhere and im overconjecturing :upside_down_face:

artemyarulin22:12:47

could be yeah. Try to find a smallest case which reproduce this error and I guess someone from this channel would help