This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
@darwin the new Dirac 1.1.0 requires Clojure 1.9 via a transitive dependency on cljs-oops. Would you consider making it an optional change? We're not ready to move to 1.9 just yet
I cannot really remove dependency on spec from cljs-oops, so your only option is to include back-ported version for Clojure 1.8, as described here: https://github.com/binaryage/cljs-oops#integrate-with-your-project
you should be able to normally depend on clojure 1.8 and add clojure-future-spec as another dependency and it should work: https://github.com/binaryage/cljs-oops-sample/blob/master/project.clj#L7
clojure-future-spec doesn't have CLJS sources
Sorry, I wasn't very clear, cljs-oops uses spec, so it forces a dependency, rather than requiring it
We're on "1.9.89"
, will check if we can upgrade
@danielcompton just so you know, you will have to add test.check
: http://dev.clojure.org/jira/browse/CLJS-1792
(which is unfortunate, but hopefully can be solved soon)
explicit clojure 1.8, latest clojure-future-spec and clojurescript 1.9.293 in your top-level project should be enough for cljs-oops to work
unfortunately I rely on spec in oops code and I’m not going to write another version without spec
btw cljs-oops
is really worth having, I am so thankful for it, I am hacking on a d3 project and I would be lost without it
@danielcompton I could release a new version of Dirac in a hour or two, with that dependency removed
which dependency?
that would be cool
if it's not too much trouble?
not really, https://github.com/binaryage/dirac/commit/a86617adaff8e5e77810ea2ee465704aa26ca61c
Thanks heaps!
@danielcompton v1.1.1 is on clojars, it will take ~15mins for chrome extension store to publish matching extension
Awesome, thanks heaps!