This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-17
Channels
- # admin-announcements (3)
- # announcements (1)
- # aws (3)
- # beginners (41)
- # boot (109)
- # braid-chat (2)
- # braveandtrue (5)
- # cider (11)
- # cljs-dev (38)
- # cljsjs (15)
- # cljsrn (5)
- # clojure (87)
- # clojure-berlin (16)
- # clojure-ireland (1)
- # clojure-japan (10)
- # clojure-madison (3)
- # clojure-nl (3)
- # clojure-poland (6)
- # clojure-russia (115)
- # clojure-sg (1)
- # clojurebridge (35)
- # clojured (8)
- # clojurescript (36)
- # core-async (24)
- # cursive (18)
- # datavis (1)
- # datomic (27)
- # dirac (22)
- # editors (1)
- # emacs (3)
- # events (19)
- # hoplon (149)
- # ldnclj (7)
- # lein-figwheel (1)
- # luminus (1)
- # off-topic (70)
- # om (196)
- # onyx (63)
- # parinfer (155)
- # proton (36)
- # re-frame (69)
- # reagent (2)
- # ring (2)
- # ring-swagger (1)
- # slack-help (4)
- # spacemacs (9)
- # testing (11)
to answer my own question from yesterday... reagent.core/props
doesn't work in a react component created via reagent.core/reactify-component
... but otherwise props work the same as with web reagent - ie they are assoc'd to the first arg to a reagent component fn
Is there any danger to calling (set! js/React (js/require "react-native”))
multiple times? I can’t seem to move om-next components to separate namespaces unless I have that statement at the top of each namespace.
@seantempesta: well, there should be no problems calling it multiple times, although you create a global here which has to be available across all your modules
Oh I see. So my components were probably just loading before that global variable was being set. Any good clojure tricks to ensuring some code is required first?
Ah, never mind. I figured it out. I’m just going to have a separate namespace that declares all the react native requires and will list that first in my requires in my core namespace.