This seems weird?

I don't think it is related to that issue, but that it probably is something Calva does. Please file an issue about it.

Will do. Thanks.

Having this in .cljfmt.edn seems to work:

{:remove-surrounding-whitespace? true
 :remove-trailing-whitespace? true
 :remove-consecutive-blank-lines? false
 :insert-missing-whitespace? false
 :align-associative? false
 #_#_:indents ^:replace {#"^\w" [[:inner 0]]}
 :indents {and [[:block 0]]
           or [[:block 0]]
           -> [[:block 0]]
           ->> [[:block 0]]
           #"" [[:inner 0]]}
 :test-code
 (long-function-name a b
   c
   d
   (and true
        false)
   (or true
       (long-function-name arg1 args2
         (->> :foo
              :bar
              (long-function-name arg1 arg2
                arg3)))))}

Something like :indents {#"^\w{4}" [[:inner 0]]} might also work.

@U0ETXRFEW What would be the reason for differences in formatting of :test-code vs. in a .clj file? Example

;; :test-code
(map a
     b)

;; .clj
(map a
  b)

:indents {reduce [[:block 0]]
           reduce-kv [[:block 0]]
           #"^\w{4}" [[:inner 0]]}

Maybe the difference is that It is nested in a map in one case and not in the other?

No, I was careful to test the same.

Very strange then. I can see no reason why it would differ.

I might give that a shot. Fixing it in nbb should fix it in joyride, right?

No, they are similar but separate projects

but both fixes should be similar

Would you prefer I file issues prior to making PRs, as per the dev doc?

We discussed it here, so it's ok to do a PR directly

I prefer an issue, actually. 😃

ok :)

one no-issue for nbb and one issue for joyride coming right up 😉

:)

Haha, awesome. It's just a thing I have, to clearly separate the problem and its solution. And to have a changelog consisting of problems handled rather than solutions or a mix of them.

I do that normally too, but I thought, let's be nice for once

@U0ETXRFEW did you notice that the auto-created changelogs in github releases list PRs (solutions) and not the issues they fix? that bothers me

I've been wondering about that.

This is why I still manually write CHANGELOG.md

I'm working on adding a CI pipeline now and am going to do the same as I do with Calva: upload the release notes from the changelog entry of the releaae.

ah I like that

Same here. Manual changelog.

Then:

BODY=$(awk '/^## \['${TAG_VERSION}'\]/, started && /^##/ { started=1; if ($0 !~ /(^#|^\s*$)/) { gsub(/["$]/, "\\\\&"); print } }' CHANGELOG.md)

I usually skip the auto-generated changelogs, people can just look in the repo

This is horrible... I'm leaving now to #babashka bye

awk is wonderful, haha

I'm going to write an awk library for Clojure some day. 😃

if you're working alone maybe

PRs are up! https://github.com/BetterThanTomorrow/joyride/pull/53, https://github.com/babashka/nbb/pull/188

I'll take a look tomorrow

Looks like you might be using an old cider-nrepl. Compare what you have in the project with what you get if you run the command Calva: Copy Jack-in Command Line to Clipboard.

I'm not using cider-nrepl at all.

Then I think that's what the error means. 😃

I don't jack-in -- I connect Calva directly to a REPL that I start in the terminal.

Ah, OK, so I need to port across my "run current test" snippet then... thanks...

That's what the copy jack-in command is for. So that you can adapt your command when starting the REPL.

Is there documentation about which commands rely on CIDER so folks who don't use it know which Calva commands won't work?

I don't want CIDER on my dev classpath thank you. I'm already unhappy that I have nREPL on it 😛

(remember: I'm coming from a plain Socket REPL where I needed no additional dependencies at all -- even having to use nrepl/nrepl pains me)

Calva depends on cider-nrepl. It's stated all over the place.

This seems to be the first command I've tripped over that depends on it tho'...

TBH, I haven't kept myself up-to-date with changes in nREPL itself. But I know some cider-nrepl stuff has been moved over there.

Nonetheless: Calva is distilled from CIDER

Feels like there should be a ™️ there 🙂

Snippets to the rescue:

(tap> (with-out-str (binding [clojure.test/*test-out* *out*] (clojure.test/test-vars [#'$top-level-defined-symbol]))))

(that's what I did with Clover)

I'm guessing you won't get the Test Explorer integration that way, but trade-offs, trade-offs.

Yeah, I am used to a particular test workflow that I got into years ago that I particularly like, where I mostly just run one test at a time, as I am working on it, and can easily run all tests in the current ns (or all tests in the -test ns associated with the current ns) with a hot key and just see the summary in Portal (previously Reveal, previously REBL).

It's kind of an extension of my "make a change, eval it" workflow where I operate in a very focused, localized way with immediate feedback.

I also have test-run snippets, btw. Because cider-nrepl still hasn't added ClojureScript support to the test runner.