This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-04
Channels
- # announcements (13)
- # beginners (51)
- # boot (3)
- # calva (10)
- # cider (20)
- # clj-kondo (55)
- # cljs-dev (60)
- # clojure (99)
- # clojure-europe (6)
- # clojure-gamedev (9)
- # clojure-italy (19)
- # clojure-nl (7)
- # clojure-spec (20)
- # clojure-uk (42)
- # clojurescript (96)
- # clojurex (37)
- # clojutre (1)
- # cursive (37)
- # data-science (2)
- # datomic (15)
- # defnpodcast (9)
- # duct (7)
- # emacs (6)
- # events (9)
- # fulcro (124)
- # jackdaw (4)
- # jobs (4)
- # leiningen (9)
- # malli (7)
- # mount (3)
- # off-topic (109)
- # other-languages (8)
- # re-frame (39)
- # reagent (4)
- # reitit (6)
- # remote-jobs (2)
- # rewrite-clj (36)
- # ring (4)
- # shadow-cljs (16)
- # spacemacs (16)
- # tools-deps (91)
- # vim (8)
- # yada (2)
I expected duct profiles provided to exec-config
to be merged in the supplied order; however it appears no explicit order is set… is that correct?!
I think we ran into this and discovered empirically that it’s potentially alphabetical, perhaps as an incidental consequence of iterating over keys in a map (not that we’d rely on that ordering)
It looks like the order is arbitrary as determined by (keys config)
(defn profile-keys
"Return a collection of keys for a configuration that excludes any profile
not present in the supplied colleciton of profiles. Profiles may be specified
as namespaced keywords, or as un-namespaced keywords, in which case only the
name will matched (e.g. `:dev` will match `:duct.profile/dev`). If the :all
keyword is supplied instead of a profile collection, all keys are returned."
[config profiles]
(cond->> (keys config)
(not= profiles :all) (filter (partial keep-key? profiles))))
surely that’s not right
left to right is what I would expect; in order of the keys in profile