Fork me on GitHub
Jakub Holý10:11:49

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 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 ...


I think this might be a an omission we should fix.

👍 1
🙏 1

Curious, do you have the trace in *e at that point?


Please file an, issue, btw. 😃

👍 1

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…


I didn’t know that parinfer broke the structure, maybe I am using the wrong options…