This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-12
Channels
- # aleph (1)
- # announcements (13)
- # asami (4)
- # babashka (47)
- # beginners (22)
- # calva (11)
- # circleci (1)
- # clj-kondo (14)
- # clojure (43)
- # clojure-europe (43)
- # clojure-gamedev (1)
- # clojure-nl (1)
- # clojure-uk (6)
- # clojurescript (13)
- # core-async (5)
- # cursive (8)
- # datomic (20)
- # events (3)
- # fulcro (12)
- # graalvm (1)
- # graphql (4)
- # gratitude (3)
- # java (2)
- # juxt (2)
- # leiningen (12)
- # off-topic (30)
- # pathom (33)
- # pedestal (5)
- # podcasts-discuss (1)
- # polylith (14)
- # rdf (2)
- # re-frame (12)
- # reagent (3)
- # releases (2)
- # shadow-cljs (24)
- # spacemacs (13)
- # sql (2)
- # tools-build (16)
Hi! when a clojure.test test fails with an exception, is there a way to see its stack trace? I only get this in the repl > ; ERROR in clj-concordion.features-test/i-fail (line 23): > ; Uncaught exception, not in assertion > ; error: clojure.lang.ExceptionInfo: fake {} (features_test.clj) > ; expected: > (throw (ex-info fake {})) > ; 1 tests finished, problems found. 😭 errors: 1, failures: 0, ns: 1, vars: 1 I'd like to see the stack trace... According to https://github.com/clojure/clojure/blob/master/src/clj/clojure/test.clj#L384 it should print the stack trace but my output stops after the "expected" part and the "actual" and stack trace are missing. In CLI (`lein test` ) I get the stack trace... There is nothing useful at https://calva.io/test-runner/ ...
No, I do not
Now that I’m drooling over the new parinfer feature, maybe another request: I would like to “format and align” function for maps to also work in “vectors-containing-pairs”, for example the bindings of a let
-block… Does that sound like a good idea?
@pez RE parinfer: I noticed that, given a file with incorrect indentation, when you edit it the brackets will be changed according to the indentation, which breaks the file. Because the indentation was wrong to begin with. I have parinfer also configured in vim, and there when I edit the same file, it will first correct the indentation before doing anything else, which solves the issue in a very nice way IMHO…
Can you add a comment about this here, @stefan.van.den.oord? https://github.com/BetterThanTomorrow/calva/pull/1381