This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-29
Channels
- # announcements (1)
- # babashka (15)
- # beginners (37)
- # calva (94)
- # cider (3)
- # clj-kondo (17)
- # cljsrn (2)
- # clojure (45)
- # clojure-europe (39)
- # clojure-germany (1)
- # clojure-norway (2)
- # clojurescript (16)
- # component (18)
- # conjure (1)
- # cursive (13)
- # datalevin (3)
- # datomic (12)
- # docker (2)
- # duct (5)
- # eastwood (2)
- # emacs (4)
- # events (8)
- # fulcro (8)
- # inf-clojure (5)
- # kaocha (8)
- # lsp (24)
- # malli (11)
- # meander (3)
- # off-topic (19)
- # polylith (11)
- # remote-jobs (4)
- # sci (61)
- # shadow-cljs (9)
- # spacemacs (34)
- # sql (10)
- # tools-deps (27)
- # xtdb (10)
@thheller If there are multiple functions in a namespace with :dev/after-load
on them, is there any way to control the order of those calls? Or is it just top to bottom? Or some random order?
(defn ^:dev/after-load a [])
(defn ^:dev/after-load b [])
;; instead
(defn ^:dev/after-load reload []
(b)
(a))
otherwise the order is undefined, given that it is constructed from analyzer data which is an unordered map
Is it expected that a custom warning is not picked up by analyzer in release
build? While it's working as expected in dev
build. Not sure if it's cljs compiler itself or something is shadow-cljs. It's not clear why it's different from dev to release builds. I guess normally one should put custom warning names into compiler options.
Nevermind, works fine :thumbsup:
Nevermind, works fine :thumbsup: