This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-20
Channels
- # adventofcode (38)
- # announcements (8)
- # aws (4)
- # babashka (131)
- # beginners (263)
- # calva (2)
- # clj-kondo (12)
- # cljdoc (12)
- # cljsrn (3)
- # clojure (122)
- # clojure-europe (3)
- # clojure-finland (2)
- # clojure-nl (13)
- # clojure-uk (80)
- # clojured (1)
- # clojuredesign-podcast (3)
- # clojurescript (78)
- # core-async (19)
- # cursive (19)
- # datomic (7)
- # duct (10)
- # events (1)
- # fulcro (7)
- # graalvm (12)
- # graphql (3)
- # juxt (4)
- # malli (10)
- # music (3)
- # nrepl (4)
- # off-topic (25)
- # pathom (4)
- # pedestal (1)
- # re-frame (78)
- # reagent (8)
- # shadow-cljs (91)
- # sql (8)
- # vim (3)
- # xtdb (2)
A couple of christmas thoughts about Aero, two common problems I had (and others as well are)
• using something like :config-value #or [#env VAR 1]
works fine locally, but when you have the $VAR set it's a string and it blows up at runtime
• just today I was confused by a problem and it was just that I had [#env VAR "val"]
instead of #or [#env VAR "vall"]
where my wrong version simply evaluated to a vector
well I guess that the second version is also potentially fine if someone actually wants a list, but I wonder if there could be a bit more safety
I can have problem spec validation everywhere, but that still would not catch the first issue, unless $VAR is set somewhere