A Brooks
A Brooks
I remember experimenting with an approach of using metadata to tag functions as reporters. I still like that idea, but I suspect it isn't a particularly high priority.
I think validation is important enough that we want to keep this feature idea open.
I thought of a pretty easy way to do this in an ad-hoc way: create aliases for the local copy of Kaocha in our own repositories, then create a small...
@colin-p-hill That's not a bad idea. I think we'd probably make it Hawk-only instead of removing it, though.
@skynet-gh @colin-p-hill I just merged a temporary fix to this issue similar to what Colin suggested. You can point Kaocha to the latest changeset `7d6c897bfd85fd66aea0c45fcbb62de37733f374` or wait until we publish...
I forgot to mention it at the time, but you can grab the latest version with the temporary fix (among other improvements): ```clojure [lambdaisland/kaocha "1.78.1249"] {lambdaisland/kaocha {:mvn/version "1.78.1249"}} ```
#404 creates the infrastructure needed to solve this issue.
I think we want to direct our focus on improving ergonomics toward making it easier to get started with kaocha-cljs2. A PR for this would be great, though.
@plexus I think this is covered by #413, although it doesn't test `kaocha-cljs` or `kaocha-cljs2` because running multiple ClojureScript test suites seems like it would be too flaky.
This is an important enough documentation gap I think it should remain open.