This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-08
Channels
- # beginners (92)
- # boot (2)
- # cljsrn (6)
- # clojure (33)
- # clojure-austin (1)
- # clojure-dev (18)
- # clojure-spec (7)
- # clojure-uk (2)
- # clojurescript (35)
- # cursive (13)
- # data-science (3)
- # datomic (1)
- # defnpodcast (1)
- # figwheel (1)
- # fulcro (27)
- # instaparse (1)
- # java (2)
- # leiningen (8)
- # off-topic (5)
- # onyx (1)
- # portkey (2)
- # re-frame (9)
- # reagent (2)
- # ring-swagger (1)
- # shadow-cljs (136)
- # test-check (3)
- # tools-deps (29)
@seancorfield what do you think about keys like :git/sha used in ctd
@alexmiller would be interested how you decided that, too
Sorry, what’s the question?
@leongrapenthin when Alex talked about that (on the list? in #tools-deps here?) he said that's a human written format so it needs to be clear but not too verbose. A while different set of considerations compared to code.
@alexmiller I'm interested in a rule when its ok to pick unqualified/unsegmented namespaces. "Lib no;app yes" seems what has emerged mostly, but in tools.deps you claim for example "git". When should a lib author choose to do this and how can he not be worried about conflicts?
Or should we say unqualifies nses in libs are reserved for core libs
@seancorfield thanks, that makes sense from a practical standpoint. I still couldn't do it in my libs without worrying about conflicts ))