dirac

Dirac v1.7.2 is out: https://github.com/binaryage/dirac/releases/tag/v1.7.2
danielcompton 2017-01-25T19:23:30.001703Z

@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

2017-01-25T19:23:45.001704Z

ah, didn’t know that

2017-01-25T19:24:17.001705Z

but I doubt it: https://github.com/binaryage/cljs-oops/blob/master/project.clj#L11

2017-01-25T19:24:45.001707Z

that “provided" should mean that your project has last word

2017-01-25T19:26:54.001709Z

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

2017-01-25T19:27:55.001711Z

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

danielcompton 2017-01-25T19:28:16.001713Z

clojure-future-spec doesn't have CLJS sources

danielcompton 2017-01-25T19:29:00.001714Z

Sorry, I wasn't very clear, cljs-oops uses spec, so it forces a dependency, rather than requiring it

2017-01-25T19:29:45.001715Z

are you using latest clojurescript? it includes cljs version of spec

2017-01-25T19:29:57.001716Z

it should be independent on clojure version, AFAIK

danielcompton 2017-01-25T19:30:35.001717Z

We're on "1.9.89", will check if we can upgrade

richiardiandrea 2017-01-25T19:31:28.001718Z

@danielcompton just so you know, you will have to add test.check: http://dev.clojure.org/jira/browse/CLJS-1792

richiardiandrea 2017-01-25T19:32:02.001719Z

(which is unfortunate, but hopefully can be solved soon)

2017-01-25T19:32:43.001720Z

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

2017-01-25T19:33:09.001721Z

unfortunately I rely on spec in oops code and I’m not going to write another version without spec

2017-01-25T19:34:30.001722Z

but maybe dirac runtime might not use cljs-oops

2017-01-25T19:36:47.001723Z

yeah, I could definitely drop the dependency on cljs-oops in dirac.runtime

richiardiandrea 2017-01-25T19:36:57.001724Z

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

😁 1
2017-01-25T19:43:55.001725Z

@danielcompton I could release a new version of Dirac in a hour or two, with that dependency removed

danielcompton 2017-01-25T19:44:18.001726Z

which dependency?

2017-01-25T19:44:28.001727Z

dirac.runtime -> cljs-oops

2017-01-25T19:44:57.001728Z

it turns out I only need oget and I can re-implement it

2017-01-25T19:45:02.001729Z

in dirac.runtime

danielcompton 2017-01-25T19:45:22.001730Z

that would be cool

danielcompton 2017-01-25T19:45:26.001731Z

if it's not too much trouble?

danielcompton 2017-01-25T19:54:09.001734Z

Thanks heaps!

2017-01-25T20:04:35.001735Z

@danielcompton v1.1.1 is on clojars, it will take ~15mins for chrome extension store to publish matching extension

2017-01-25T20:05:00.001736Z

but those two will work together: 1.1.0 extension and 1.1.1 runtime

danielcompton 2017-01-25T21:01:19.001744Z

Awesome, thanks heaps!

👍 1