This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-21
Channels
- # announcements (20)
- # beginners (31)
- # biff (8)
- # cherry (5)
- # cider (4)
- # cljs-dev (1)
- # clojure (26)
- # clojure-australia (2)
- # clojure-europe (16)
- # clojure-spec (10)
- # community-development (8)
- # conjure (1)
- # core-async (1)
- # data-oriented-programming (1)
- # data-science (54)
- # datascript (10)
- # fulcro (1)
- # graalvm (2)
- # malli (5)
- # off-topic (3)
- # pathom (23)
- # rdf (1)
- # re-frame (6)
- # reitit (11)
- # shadow-cljs (6)
- # squint (2)
- # xtdb (33)
That's helpful, thank you. And it seems (:shadow.build/mode &env)
is nil
when shadow is watch
ing a build and hot reloading a namespace, is that expected?
Actually i'm sometimes getting nil values for (:shadow.build/mode &env)
inside macros, even when doing a release build. it's almost like there is some kind of compliation pass that happens which causes macroexpansion before the build environment is set. I also noticed that there are some macroexpansions that happen before the :configure
stage of hooks are called.
there can be no macro expansions before :configure
. well unless those macros are in .cljc and you do anything in CLJ?
needless to say it is only set for CLJS compilation. otherwise it won't be present, but it should always be present for CLJS code?