This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
It would really be great if we didn't make breaking changes for only aesthetic reasons
when I do
cider-connect-clojurescript it asks me to associate with a project, it doesn't seem to do this with
cider-connect (clojurescript). Does it infer something different with clojure projects vs clojurescript ones?
Just started seeing this error when I do
I'm using the latest version of cider, and as the repl starts I see it is using cider/cider-nrepl "0.18.0-SNAPSHOT" not 1.0.0. This project was working fine a few hours ago. Doing a package update of cider (I was a day behind) didn't change anything. Any ideas?
WARNING: CIDER's version (0.18.0-snapshot) does not match cider-nrepl's version (1.0.0). Things will break!
This was supposed to extract the version of
cider-nrepl from the artifact’s metadata.
You can ignore the warning. I’ll revert the change if I can’t figure out what went wrong.
> It would really be great if we didn’t make breaking changes for only aesthetic reasons (edited)
So it should still work ok? My project is no longer working, looks like none of my re-frame :events are getting registered. Maybe I broke something unrelated...
@bhauman Sure. Generally I just want to avoid having to test on a huge build matrix and have to do weird compatibility tricks. I’m fine with maintaining Clojure 1.7 if someone starts complaining about this, but I really don’t think we need to bother with JDKs that have reached their EOL 5 years ago.
@soulflyer I can’t imagine how this can be the problem. It’s a one-liner type of change.
It’s a pity that it’s so hard to be able to leverage the project’s version declaration internally. 😄
ah-ha. all good now. clj-refactor had moved the subs :require out of my core.cljs. Absolutely nothing to do with cider-nrepl at all....