This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-05
Channels
- # aws (6)
- # beginners (10)
- # boot (33)
- # cider (23)
- # cljs-dev (50)
- # cljsjs (2)
- # cljsrn (10)
- # clojars (1)
- # clojure (215)
- # clojure-czech (1)
- # clojure-dev (5)
- # clojure-italy (23)
- # clojure-russia (18)
- # clojure-spec (11)
- # clojure-uk (53)
- # clojurescript (157)
- # core-async (29)
- # cursive (12)
- # data-science (15)
- # datascript (16)
- # datomic (68)
- # graphql (2)
- # jobs (5)
- # jobs-discuss (1)
- # juxt (17)
- # lein-figwheel (2)
- # luminus (3)
- # off-topic (155)
- # om (3)
- # pedestal (1)
- # portkey (1)
- # re-frame (7)
- # reagent (4)
- # ring (3)
- # ring-swagger (2)
- # rum (11)
- # unrepl (11)
- # vim (1)
- # yada (2)
Just to echo some issue I encountered with the split/spec.alpha ns. I
had to upgrade projects with dependencies that also depended on
clj.spec (pre split), hoping to use the latest clojure alpha. This
caused exceptions to be raised on non existing namespace from
(numerous) transitive deps and forced me to chase down every single
ref in the transitive deps before I could do anything (creating custom
jars for these etc etc). Not to mention namespaced keywords impacted.
Before that would have been a simple :exclusions
in the project.clj
and done. I understand the intention but to be honest the new
"namespace versioning" is quite annoying to deal with day to day, and
I guess this will continue as we go from alpha -> beta -> rc -> vN ? and
potentially be more annoying down the road as/if user adopt spec more.
maybe having a clojure.spec namespace that aliases to the versioned version wouldn't hurt.
@mpenet there will just be a 1-time addition of non-alpha namespaces in the future. Existing alpha namspaces will continue to work for as long as you include the alpha lib.