This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-11
Channels
- # announcements (5)
- # babashka (43)
- # beginners (78)
- # calva (1)
- # cider (35)
- # clj-kondo (15)
- # clj-otel (3)
- # cljs-dev (2)
- # clojure (24)
- # clojure-denmark (1)
- # clojure-dev (9)
- # clojure-europe (43)
- # clojure-israel (1)
- # clojure-italy (1)
- # clojure-losangeles (3)
- # clojure-nl (1)
- # clojure-norway (54)
- # clojure-romania (1)
- # clojure-uk (2)
- # clojurescript (1)
- # core-async (25)
- # cursive (7)
- # datascript (6)
- # datomic (7)
- # docker (2)
- # emacs (2)
- # events (8)
- # exercism (2)
- # fulcro (2)
- # hyperfiddle (16)
- # lsp (46)
- # malli (10)
- # membrane (2)
- # music (6)
- # nbb (30)
- # off-topic (49)
- # polylith (4)
- # reagent (3)
- # releases (4)
- # shadow-cljs (5)
- # slack-help (1)
- # sql (2)
- # testing (2)
- # timbre (6)
- # tools-deps (29)
- # xtdb (36)
I require
d a namespace under an alias a
in a comment
block, but code completion listed functions for a completely different namespace for a/
. Then I tried require
ing this namespace in the top level ns
form instead but now code complete says "No suggestions` for a/
. I noticed that this namespace is one from an extra-deps in my ~/.clojure/deps.edn
and aliases to namespaces from libs in my project's deps.edn
correctly code-complete
I wanted to run the tests Cursive and hoped for test output like shown in https://cursive-ide.com/userguide/testing.html , however nothing at all is shown in the code view, the only thing I see is Ran 1 test containing 2 assertions. 1 failure, 0 errors.
in the REPL, no description at all on what the failure was about.
However what I do get is the error in the picture as a popup, "Unable to apply parinfer to DUMMY.clj due to inconsistent indentation" does that have something to do with it? If I turn parinfer off, I don't get that error anymore, but still no test failure descriptions
I believe the "no description of the failure in the REPL" is 'normal' behavior. The screenshots from the website show an exception that was thrown in the REPL (which is an error rather than a failure). The page goes on to say that the tests in the current ns get annotated (in the editor), and a mouseover or an invocation of "error description" (ctrl + F1 by default I believe) gives (at least in my case) the message "Assertion failed", plus the msg
param, and an option to view the diff between expected and actual (at least in some cases)
As I said, I don't see anything at all about the test failure. No way to figure out what went wrong with the test. Basically Cursive test integration seems to not be working at all except for being able to run them.
@UCULU82G3 Sorry about this, I’m hoping to look at this tomorrow or the day after. Which OS are you on? I suspect this might be a windows issue.
@UCULU82G3 The fix for this is out now in eap8, try it out and let me know if it works for you. There’s info here about how to use an EAP build if you’re not already: https://cursive-ide.com/userguide/#choosing-to-receive-eap-beta-builds