This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-13
Channels
- # admin-announcements (6)
- # beginners (51)
- # boot (164)
- # braid-chat (49)
- # cider (10)
- # clara (17)
- # cljs-dev (13)
- # cljsjs (51)
- # cljsrn (10)
- # clojars (42)
- # clojure (195)
- # clojure-bangladesh (102)
- # clojure-berlin (8)
- # clojure-canada (1)
- # clojure-chicago (19)
- # clojure-colombia (4)
- # clojure-denmark (6)
- # clojure-russia (15)
- # clojure-ukraine (7)
- # clojurescript (257)
- # code-reviews (10)
- # community-development (292)
- # core-async (13)
- # datomic (26)
- # dirac (4)
- # dunaj (5)
- # dysphemism (5)
- # events (21)
- # funcool (15)
- # hoplon (115)
- # instaparse (31)
- # ldnclj (15)
- # mori-fork (43)
- # mount (5)
- # off-topic (18)
- # om (195)
- # onyx (13)
- # proton (9)
- # re-frame (11)
- # reagent (44)
- # slack-help (14)
- # slackpocalypse (1)
- # spacemacs (10)
- # yada (23)
usually, depending on the app, you would have the first ns
where everything is started from. it can be a handler for web apps, or -main
, or something else
I suspect the actual placement would not matter in cljs
, since it will become one big file anyway, but it would depend on whether the goog.require
s precede the expanded version of defstate
@tolitius: Hm. I tried putting (:require [mount.core])
only in my main mount-question.core
ns which :refer
s the other one where the warning occurs (`mount-question.config` in the minimal example) ... and the warning appears. But if I move (:require [mount.core])
back to mount-question.config
ns instead, it's happy. In my real app, config
is the bottom-most dependency that everyone else ultimately relies on. So it looks like putting it in the main ns is not as 'early' as putting it in the bottom-most ns that needs to be defined first?