This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-26
Channels
- # adventofcode (2)
- # beginners (69)
- # boot (37)
- # cider (6)
- # clara (31)
- # cljs-dev (75)
- # cljsrn (5)
- # clojure (72)
- # clojure-dev (7)
- # clojure-italy (11)
- # clojure-nl (8)
- # clojure-russia (2)
- # clojure-spec (56)
- # clojure-uk (54)
- # clojure-za (1)
- # clojurescript (156)
- # cursive (2)
- # datomic (34)
- # emacs (1)
- # fulcro (227)
- # hoplon (74)
- # jobs (1)
- # jobs-discuss (16)
- # leiningen (5)
- # lumo (17)
- # off-topic (9)
- # om (3)
- # onyx (10)
- # other-languages (1)
- # portkey (2)
- # re-frame (2)
- # reagent (36)
- # reitit (1)
- # remote-jobs (1)
- # ring-swagger (8)
- # shadow-cljs (85)
- # slack-help (2)
- # spacemacs (6)
- # specter (3)
- # sql (17)
- # test-check (15)
- # tools-deps (80)
Setting :pedantic? false
in profiles.clj works, but it will warn the following: (:abort and false have a type mismatch merging profiles.)
What would be the proper way to override :pedantic?
?
what's the correct way for a plugin to make modifications (e.g., add deps) that only affects development? is it for the plugin itself to somehow ensure this, by adding things to the dev profile (which seems problematic), or is it better for the plugin to be agnostic and the user to enforce it by putting the plugin itself in the dev profile?
Is the plugin being called directly by the user, or is it adding them implicitly when the plugin is loaded?
um, I think I have a use for both
e.g., consider adding repl functionality that includes deps