This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # beginners (167)
- # boot (117)
- # boulder-clojurians (1)
- # cbus (1)
- # clara (3)
- # clojure (87)
- # clojure-conj (2)
- # clojure-japan (2)
- # clojure-russia (23)
- # clojure-spain (3)
- # clojure-za (2)
- # clojurescript (184)
- # community-development (8)
- # core-async (7)
- # core-matrix (4)
- # cursive (36)
- # data-science (74)
- # datascript (3)
- # datomic (171)
- # events (6)
- # hoplon (83)
- # ldnclj (5)
- # ldnproclodo (1)
- # lein-figwheel (2)
- # leiningen (19)
- # liberator (2)
- # off-topic (5)
- # om (227)
- # onyx (5)
- # re-frame (142)
- # reagent (4)
- # yada (5)
The update plugin in IntelliJ messed up again. Where can I download the latest cursive plugin (0.1.67) so I can install it manually?
See the "Manually installing Cursive" section here: https://cursiveclojure.com/userguide/
is there a way to get cursive test runners to use 'pjstadig/humane-test-output'? The only output i see from 'run tests in current NS in REPL' is:
Loading test/clj/handler_test.clj... done Running handler-test/my-test Ran 1 test containing 1 assertion. 1 failure, 0 errors.
but when i use
(run-tests) in the same NS, I see the expected output:
FAIL in (my-test) (handler_test.clj:103) expected: [1 2] actual: [2 3] diff: - [1 2] + [2 3]
:dependencies [[pjstadig/humane-test-output "0.7.0"]] :injections [(require 'pjstadig.humane-test-output) (pjstadig.humane-test-output/activate!)]
Upgraded to Cursive 0.1.67 this morning. When I run a lein task, it creates a background task “Calculating task classpath” that never ends. Never gets to my task 😢.
the ‘pdo’ plugin doesn’t run inside cursive tasks either… maybe it’s plugins that are the problem.
Plugins should work, I’ve been testing with a bunch of them, but the new integration is a big change so perhaps these do something differently.
I’ve got to go get the family ready, but if you could send a repro project I’ll look at it this morning.
That repo should be ready to go. I did a fresh checkout and confirmed it exhibits the problems.
spec (locked) - starts the “Calculating task classpath” background taks that never ends.
The spec tasks is defined here: https://github.com/slagyr/speclj/blob/master/src/leiningen/spec.clj
@sashton: Normally for running tests interactively, the best thing to do is to click on the failure icon in the gutter, and Cursive will show a visual diff of the expected and actual values.
I’ve heard that it may not interact well with humane-test-output though, so if you find that doesn’t work, try disabling that.