Not on my laptop but check this namespace. Does it know about bb files? (:require [clojure.tools.namespace.find :as find]

> Is it possible for babashka test files to also be .bb instead of .clj? Yes, the search order is .bb, .clj, .cljc

but tools.namespace probably doesn't search for that

so that's why the test runner doesn't do what you want

another solution to this is to split out the bb tests in a separate directory and then use the test runner on that directory instead

or use reader conditionals to make .clj files both jvm + bb compatible (and renaming them to .cljc)

I'm not sure what you mean by the separate directory bit? They're already in a separate directory within our repo. It looks like actually I could make this work if, before invoking cognitect.test-runner.api/test, I with-redefs'd clojure.tools.namespace.file/clojure-extensions to include .bb. I wonder if that's doable within :task in bb.edn

What I mean that instead of putting all your tests in test/... you put your bb-specific tests in test-bb and then use :paths ["test-bb"] + --dir test-bb in the test runner

so use a different classpath for bb

oh sure, you could do the with-redefs

With our CI actions I mean it recursively scans all the directories in the repo and every time it finds a 'clojure' file (based on extension) it marks that directory as one to be acted on, and adds it to the classpath when certain actions are run. So changing the directory to test-bb but containing .clj files would just mean test-bb got added to the classpath on CI 🙂

k

Woop woop! 🎉 Thank you!

➜ bb test:bb

Running tests in #{"test"}

Testing securityhub.core-test

Testing securityhub.finding-test

Testing securityhub.slack-test

Testing securityhub.url-test

Ran 14 tests containing 32 assertions.
0 failures, 0 errors.

➜ mv test/securityhub/core_test.clj test/securityhub/core_test.bb

➜ bb test:bb

Running tests in #{"test"}

Testing securityhub.core-test

Testing securityhub.finding-test

Testing securityhub.slack-test

Testing securityhub.url-test

Ran 14 tests containing 32 assertions.
0 failures, 0 errors.

{test:bb {:extra-paths ["test"]
                  :extra-deps {io.github.cognitect-labs/test-runner {:git/tag "v0.5.1" :git/sha "dfb30dd"}
                               org.clojure/tools.namespace {:mvn/version "1.3.0"}}
                  :requires ([clojure.tools.namespace.file :as file])
                  :task (with-redefs [file/clojure-extensions (list ".bb" ".clj" ".cljc")]
                          (exec 'cognitect.test-runner.api/test))
                  :exec-args {:dirs ["test"]}
                  :org.babashka/cli {:coerce {:nses [:symbol]
                                              :vars [:symbol]}}}}

nice :)

Perhaps this is possible by changing babashka.process/defaults and setting :out to *out*

Yeah that would definitely do it. I think I will try to figure out how to do that via command line args to babashka so that I do not have to edit the script. Will report back if I figure it out. Thanks!

first try if this helps at all, before figuring out how to do it via the command line

that might save you some time in case it doesn't work ;)

Thanks for helping me think it through. I think what I really want is for :out :inherit to stream to my Cider REPL. I think this would probably require me to start the bb process from inside Emacs, which seems like too heavy of a lift for such a small issue

Looks like a possible route would be to use cider-jack-in with bb nrepl server and (setq cider-redirect-server-output-to-repl t) , but some additional logic from the cider-nrepl middleware would have to be added to the babashka nrepl-server

you can first try it with babashka.process on the JVM and regular nrepl middleware perhaps

This is giving me flashbacks :-) I did this with jq and sed in the past: • get current version by parsing json • search and replace the version string with new value (more or less)

Although I think since then jq gained the ability to update values while preserving order I think

you can parse this as yaml, yaml uses ordered collections so it might preserve stuff better

$ bb -e '(-> (clj-yaml.core/parse-string "{a: 1, b: 2}") (assoc :a 2) (clj-yaml.core/generate-string))'
"{a: 2, b: 2}\n"

With more than 8 kvs:

bb -e '(-> (cheshire.core/parse-string "{\"a\": 1, \"b\": 2, \"c\": 2, \"d\": 2, \"e\": 2, \"f\": 2, \"g\": 2, \"i\": 2}") (assoc :a 2) (cheshire.core/generate-string))'
"{\"d\":2,\"f\":2,\"e\":2,\"a\":1,\"i\":2,\"b\":2,\"g\":2,\"c\":2,\"a\":2}"

$ bb -e '(-> (clj-yaml.core/parse-string "{\"a\": 1, \"b\": 2, \"c\": 2, \"d\": 2, \"e\": 2, \"f\": 2, \"g\": 2, \"i\": 2}") (assoc :a 2) (clj-yaml.core/generate-string))'
"{a: 2, b: 2, c: 2, d: 2, e: 2, f: 2, g: 2, i: 2}\n"

if you replace the last call to cheshire.core/generate-string then it will also output valid json but still in the right order

but you can also just use npm version <new-version>:

borkdude@MBP2019 /tmp/proj $ npm version v0.1.2
v0.1.2
borkdude@MBP2019 /tmp/proj $ cat package.json
{
  "version": "0.1.2"
}
borkdude@MBP2019 /tmp/proj $ npm version v0.1.3
v0.1.3
borkdude@MBP2019 /tmp/proj $ cat package.json
{
  "version": "0.1.3"
}

you can do this from bb with: (babashka.process/shell "npm version" version)

Thank you team!!

+1 on clj-yaml – it uses an ordered-map in the background to achieve this

Just briefly looked at it, seems like npm version simply deserializes and reserializes package.json

Which means key order is preserved (because unlike Clojure maps, JS objects preserve insertion order)

Indentation, however, is removed

Comments would be removed too, but fortunately JSON has no comments 🙂