This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-10
Channels
- # beginners (35)
- # cider (165)
- # cljsrn (18)
- # clojars (1)
- # clojure (141)
- # clojure-greece (2)
- # clojure-italy (11)
- # clojure-nl (1)
- # clojure-spec (21)
- # clojure-uk (89)
- # clojurescript (56)
- # community-development (3)
- # cursive (3)
- # data-science (55)
- # datomic (13)
- # emacs (12)
- # fulcro (31)
- # graphql (6)
- # jobs-discuss (35)
- # lein-figwheel (10)
- # mount (2)
- # off-topic (3)
- # onyx (22)
- # parinfer (4)
- # portkey (7)
- # re-frame (29)
- # ring-swagger (4)
- # shadow-cljs (37)
- # specter (9)
- # sql (30)
- # tools-deps (15)
- # vim (2)
- # yada (17)
@alexmiller: I’m bike shedding a little but what would you recommend calling the key for lein-tools-deps
config. Currently it’s called :tools/deps
which feels a little wrong, should it be :lein.tools/deps
or :lein.tools.deps
, or just :lein-tools-deps
?
This is the key for using in a project.clj
for configuring how the lein-tools-deps
plugin should work with tools.deps
should be namespaced
wait, this is in project.clj?
I guess most stuff there is not namespaced
saying “lein” seems redundant
I guess I’d say :lein-tools-deps
or :tools-deps
yeah its in project.clj
but thought it might be nice to set a precedent
:lein-tools-deps/config
yeah I had thought of that one too… I like that it nests config under it, but it gets wordy… though that’s not really an issue
it also matches the actual project name on github, and root namespace name
I think that’s definitely the most correct one
thanks