rcf VS clojure-style-guide

After doing some interactive development, I will occasionally reuse some of this example code and make it into actual, formalised tests in the test namespaces. Some people have started using the comment form for actual tests too, e.g. hyperfiddle/rcf or matthewdowney/rich-comment-tests.

Test lib is https://github.com/hyperfiddle/rcf, which had a release last week – the release is a noop from userland but has a bunch of infrastructure we need (RCF now implements the Clojure/Script analyzer to extend Clojure syntax so that (do x := y) is an async test assertion at any depth in the form.)

Not to make you feel too bad, but based on your sentence you may appreciate a recent addition to my personal REPL toolkit in Clojure which I very much enjoy.

You may remember the rich comment forms in Clojure development as a communication tool to your future self and others. Now someone made them testable https://github.com/hyperfiddle/rcf#readme

I use shadow-cljs server for both node and browser, the REPL is instant. There is some configuring though, you can probably get help in slack. (Shameless plug – JS has lots of async, to tame that at the REPL try https://github.com/hyperfiddle/rcf)

If you have concerns about the correctness of get-book-tags in isolation I would suggest https://github.com/hyperfiddle/rcf,

Based on https://github.com/hyperfiddle/rcf, a REPL-first test macro for Clojure/Script which turns your Rich Comment Forms into tests (in the same file as your functions). It's good, try it!

Fixed link to that style guide entry: https://guide.clojure.style/#opt-commas-in-map-literals

Per that style guide, the above map would be formatted like this (on HN, just indent by two spaces):

  {:a 1

As for the broader question of Clojure style, there are style guides like https://github.com/bbatsov/clojure-style-guide and tools like clj-kondo to help learn and reinforce important practices.

Basically, you learn the expected places to put whitespace, make sure to edit your code accordingly and all of the parens will be automatically closed and adjusted. Using parinfer—which you can also combine with the more traditional paredit—makes writing Clojure code a lot like writing Python.

Also, there are guidelines, the styleguide, clj-kondo, kibit etc. And if you don't review your interns/juniors code to teach them good practices - you're doing it wrong (well, this one is true for any practical PL out there).

Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.

It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-guide

The same could be said about the "Clojure Style Guide" from the Cider guy. As a matter of fact, there was an issue about it that was quickly declined https://github.com/bbatsov/clojure-style-guide/issues/232

Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw