@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
ah, didn’t know that
but I doubt it: https://github.com/binaryage/cljs-oops/blob/master/project.clj#L11
that “provided" should mean that your project has last word
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
are you using latest clojurescript? it includes cljs version of spec
it should be independent on clojure version, AFAIK
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
but maybe dirac runtime might not use cljs-oops
yeah, I could definitely drop the dependency on cljs-oops in dirac.runtime
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?
dirac.runtime -> cljs-oops
it turns out I only need oget
and I can re-implement it
in dirac.runtime
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
but those two will work together: 1.1.0 extension and 1.1.1 runtime
Awesome, thanks heaps!