This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-28
Channels
- # aatree (1)
- # admin-announcements (5)
- # beginners (5)
- # braid-chat (2)
- # cbus (2)
- # cljs-dev (8)
- # cljsrn (13)
- # clojure (101)
- # clojure-chicago (1)
- # clojure-greece (11)
- # clojure-russia (77)
- # clojure-taiwan (1)
- # clojure-uk (5)
- # clojurescript (73)
- # core-async (5)
- # core-matrix (1)
- # cursive (5)
- # datomic (10)
- # devcards (44)
- # emacs (16)
- # hoplon (207)
- # keechma (5)
- # lein-figwheel (1)
- # leiningen (5)
- # liberator (3)
- # melbourne (1)
- # om (171)
- # onyx (25)
- # parinfer (1)
- # proton (2)
- # re-frame (28)
- # reagent (50)
- # untangled (7)
- # yada (4)
to answer my question:
re-natal use-component realm/react-native
and then
(set! js/RealmReactNative (js/require "realm/react-native"))
@michaelr: glad you worked this out, but there might be an issue with global assignment when you run your app with offline bundle like this https://github.com/drapanjanas/re-natal/issues/32 Is it not working with local var? (def RealmReactNative (js/require "realm/react-native”))
i'll check that issue, not sure if i tried using local var, so far just followed the (set!) convention
Yeah, that issue popped up yesterday, I still have no clue why suddenly global assignment of React started to crash
React variable is a bit special, because reagent needs that as far as I remember. But other stuff should not need to be global