This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-30
Channels
- # arachne (23)
- # bangalore-clj (2)
- # beginners (64)
- # boot (20)
- # cider (3)
- # clara (11)
- # cljs-dev (29)
- # cljsrn (10)
- # clojure (143)
- # clojure-brasil (4)
- # clojure-dev (22)
- # clojure-dusseldorf (3)
- # clojure-italy (26)
- # clojure-sanfrancisco (13)
- # clojure-seattle-old (2)
- # clojure-spec (15)
- # clojure-uk (27)
- # clojured (1)
- # clojurescript (52)
- # core-async (13)
- # cursive (2)
- # datomic (106)
- # fulcro (45)
- # garden (1)
- # graphql (11)
- # hoplon (98)
- # jobs (11)
- # juxt (7)
- # keechma (2)
- # leiningen (36)
- # off-topic (39)
- # parinfer (13)
- # re-frame (34)
- # reagent (5)
- # ring (1)
- # rum (4)
- # shadow-cljs (83)
- # sql (1)
- # timbre (1)
- # unrepl (49)
- # vim (1)
- # yada (42)
@tcoupland I will try to summon @martintrojer who would be more qualified to answer that. Personally I haven't used joplin so I'm unsure. It was a library we built on our http://OnTheMarket.com project
@tcoupland es is a fast moving target. Personally I'd just re-write all this using a regular http client or a lib based on one, this is more future-proof
we have schemas/migration that work for 2.4+ and 5.x+ using such a lib, this requires just a couple of conditions/switches and it's all dealt at the data level, not api. It's much nicer imho
fast moving: by the time we supported 5.x 6.x was coming out, with it's lot of breaking changes
with aero, read-config
would throw an error if there’s a type coercion on an env var and the env var doesn’t exist (expectedly so), if I have a multi-profile config, how do I deal with this not breaking in environments like dev where these env vars don’t exist and are coded-in as a part of the config? is there a generally a better pattern to deal with a situation like this?