orchard icon indicating copy to clipboard operation
orchard copied to clipboard

Run test suite for :cljs branches

Open vemv opened this issue 2 years ago • 5 comments

There are a few :cljs branches in our reader conditionals, but there isn't a cljs runner in our CI.

This means an important hole in test coverage.

(Thanks for spotting this @lread)

vemv avatar Jan 23 '22 23:01 vemv

The context is me looking into an issue @vemv raised on cljdoc. He had an awesome idea that I was exploring, and initial experiments look promising for cljdoc Clojure analysis. But when the cljdoc analyzer saw cljc files in orchard, it tried ClojureScript analysis and that failed. I was wondering if this failure was cljdoc's or orchard's.

So I dug into orchard (a very wee bit) to see if there were cljs tests. I do see test-cljs/orchard/cljs but don't understand if/how these are run.

lread avatar Jan 24 '22 15:01 lread

FWIW, cljdoc now allows you to select which languages are analyzed. To only have cljdoc analyze for clj (and not cljs), a ./doc/cljdoc.edn with the following contents should do the trick:

{:cljdoc/languages ["clj"]}

Lemme know if you want a PR.

lread avatar Mar 03 '22 18:03 lread

Nice feature!

PR would be perfect, thanks! Same for cider-nrepl, refactor-nrepl

vemv avatar Mar 03 '22 23:03 vemv

PR would be perfect, thanks! Same for cider-nrepl, refactor-nrepl

@vemv, PR done for this repo, for your next release to clojars, cljdoc should build fine, feel free to ping me if there are any issues.

I had a quick look at the following for you:

  • cider-nrepl - seems like cljdoc is failing to analyze for clj so not the same issue.
  • refactor-nrepl - also a clj analysis failure Lemme know if you want help getting these working on cljdoc and we'll see what we can do, but probably better to visit cljdoc slack channel and/or raise cljdoc GitHub issues.

lread avatar Mar 04 '22 19:03 lread

Cheers! 🍻

Both projects depend on Orchard, so starting there seems on the safe side.

vemv avatar Mar 05 '22 01:03 vemv