This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # announcements (1)
- # babashka (130)
- # beginners (120)
- # calva (11)
- # cider (5)
- # clj-kondo (9)
- # cljsrn (17)
- # clojure (63)
- # clojure-australia (1)
- # clojure-canada (21)
- # clojure-europe (37)
- # clojure-israel (4)
- # clojure-uk (6)
- # clojurescript (170)
- # conjure (5)
- # core-async (23)
- # cursive (16)
- # datomic (4)
- # defnpodcast (1)
- # emacs (5)
- # fulcro (1)
- # gis (2)
- # graalvm (31)
- # graphql (4)
- # helix (6)
- # honeysql (16)
- # jobs-discuss (3)
- # juxt (1)
- # lsp (7)
- # malli (20)
- # meander (12)
- # missionary (6)
- # off-topic (50)
- # pathom (4)
- # re-frame (4)
- # react (1)
- # ring (2)
- # shadow-cljs (63)
- # spacemacs (2)
- # sql (15)
- # testing (6)
- # vim (8)
- # xtdb (7)
@cfleming i was reporting an issue with paren highlighting back in april:
i've found the cause of the phenomena!
Use block caret
if it's ON, the highlighted matching paren is the unexpected one.
if it's OFF, then it works as advertised.
i tried to find a related github issue to note this finding there, but i couldn't.
i had this cursive doc page open on my machine for some reason: https://cursive-ide.com/userguide/repl.html and i've noticed that in the animated images, the caret was a bar, not a block. that gave me the idea
Hmm, interesting - have you searched in YouTrack? That sounds like an IntelliJ issue to me.
Added a comment here: https://youtrack.jetbrains.com/issue/IDEA-215291#focus=Comments-27-4965809.0-0
Is there any way to see the detail of a test failure in REPL? I know I can see them in a tooltip, but it’s a little hassle to navigate to the test code.
this has been discussed before, but unfortunately there is no way to do that now. what i didn't know though, is that it's slightly easier to get to the test failure if your gutter is on and click the fail-icon there. u don't have to hover and wait at least for the dialog with the link to the diff.
otherwise, i've hooked up
kaocha.repl/run to a REPL command and then assigned it to Cmd-R to conveniently run tests.
it was not a great choice of keyboard shortcut because i often restart the REPL accidentally 🙂
but other than that, it's a pretty pleasant workflow.
i wish i wouldn't need to carry a koacha setup around for every project, but that's the best i could come up so far
here is a related issue: https://github.com/cursive-ide/cursive/issues/2229
btw, do u know that you can run clojure tests using the same machinery provided to other languages in intellij? u have to create a run configuration for the tests u want to run and wait for your clojure app to start up, so it's slower than a repl-based approach, but it's also cleaner, because u are guaranteed not to have any misleading REPL state affecting your tests. it's documented here: https://cursive-ide.com/userguide/testing.html#test-runner
Yes, the problem is starting up a REPL in my test is very slow because of a lot of initial setups.
I didn’t know that there’s already an issue. Yes, checking a diff is also another pain point. I don’t want to use my mouse to check the test result basically.
anyone knows how to print diffs on IntelliJ when using Nubank Matcher Combinators?
I will just manually run the test in the REPL and inspect the printed output. Don't know if there's a better way.
and unfortunately the output is not as nice as using the built-in kaocha support for the
i was just asking about this on the kaocha channel the other day and got this response:
> actuallyalys_slack: I think we could use better documentation for matcher-combinator support. I'll write up an issue.
this was my question: