This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (135)
- # announcements (1)
- # beginners (192)
- # boot (5)
- # calva (130)
- # cider (42)
- # cljdoc (4)
- # cljs-dev (6)
- # cljsrn (3)
- # clojure (222)
- # clojure-europe (2)
- # clojure-greece (5)
- # clojure-italy (24)
- # clojure-nl (23)
- # clojure-russia (1)
- # clojure-spec (6)
- # clojure-uk (67)
- # clojurescript (35)
- # cursive (39)
- # datomic (61)
- # emacs (17)
- # figwheel (3)
- # figwheel-main (2)
- # fulcro (12)
- # hyperfiddle (10)
- # juxt (3)
- # leiningen (10)
- # nrepl (35)
- # off-topic (34)
- # onyx (3)
- # pathom (6)
- # quil (5)
- # re-frame (29)
- # reitit (6)
- # ring (1)
- # ring-swagger (8)
- # shadow-cljs (37)
- # spacemacs (9)
- # sql (9)
- # tools-deps (24)
- # unrepl (1)
- # vim (1)
@cfleming Hey Colin, I removed the target directory, the .cp directory and the project.clj that I had previously renamed project.clj.back don’t ask why... It seems to work fine now. My guess would be that some artifacts generated previously using lein might have messed things up a bit. I don’t know if that make sense though. Still it works! Thanks.
Feature request (or, is this already possible?): - click on a test assertion failure (yellow “!” icon) - assertion diff window pops up (now for the feature request) - if the same test is re-run, and a new diff is produced, update the existing diff viewer with the new results, so the user doesn’t have to navigate back to the file and click the icon again
BTW @alexmiller, following on somewhat from the discussion in #clojure, I remember you have mentioned a couple of times that you don’t like how Cursive presents exceptions, but I can’t remember the details. What would you like to see there?
The number one thing is that Cursive shows only the top exception in the chain, whereas 100% of the time I want the root cause, so I find the default behavior to completely hide the useful info
Now with 1.10, I’d love to see all the work we did on messages and ex-data get used
Right, at the moment it just uses
*e. I’ll look at fixing that, and I’ll look at what I can do in 1.10 too.
https://clojure.org/reference/repl_and_main now has a new section on error stuff
I have a namespace
compute.alerts.test-utils located in my
test directory. I have a
dev.play in my
siderail directory. If the
dev.play ns looks like this:
with my cursor where the | is, I do not get any auto complete -- it says "No suggestions". There are definitely public functions in
(ns dev.play (:require [compute.alerts.test-utils :as test])) (test/|)
compute.alerts.test-utils. I have tried File > Invalidate caches & restart, which does not help. Any ideas?
@kenny I can’t think of anything immediately, no. Both
siderail are marked as source roots?
I also tried creating another namespace in the
test directory and it doesn't auto complete either.
Actually, isn’t it expected that you can’t access test sources from source root files?
Hmm, it’s possible there’s some assumption about that baked into Cursive, I’ll take a look.
Actually, that may even be baked into IntelliJ, now that I think about it - it’s been a while.
Hmm. That distinction seems confusing. In my mind things are either on the classpath or they aren't. If they're on the classpath, I'd expect auto complete to work.
test2 to my
:extra-paths and I get auto complete from
compute.alerts.test-utils. Sounds like your guess along the right lines.
Ok, I’ll take a look. Often these things are more fluid in Clojure than e.g. in Java.
But from Cursive’s point of view, once something is marked as a source root it has no way of knowing if it was marked as such in
That seems ok. It sounds like the problem is you do not get auto complete from namespaces defined in a test root when working in a sources root.
Yes, I think that should be allowed, perhaps with an inspection to warn that you’re doing that (since it might be unexpected).