This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-24
Channels
- # announcements (2)
- # beginners (131)
- # calva (4)
- # cider (29)
- # cljs-dev (18)
- # cljsrn (8)
- # clojure (61)
- # clojure-czech (1)
- # clojure-europe (5)
- # clojure-italy (14)
- # clojure-nl (6)
- # clojure-switzerland (2)
- # clojure-uk (125)
- # clojuredesign-podcast (10)
- # clojurescript (25)
- # clojutre (15)
- # clr (4)
- # code-reviews (4)
- # data-science (1)
- # emacs (1)
- # events (2)
- # fulcro (12)
- # graalvm (4)
- # jobs (2)
- # keechma (1)
- # off-topic (1)
- # pathom (18)
- # re-frame (3)
- # reagent (7)
- # shadow-cljs (106)
- # spacemacs (33)
- # sql (12)
- # xtdb (5)
is there a way to generate test coverage reports for Clojurescript code?
it's quite easy on the jvm but I can't find anything for Clojurescript
hmm testing? like a result file with how all the tests went?
mm no I mean the equivalent of https://github.com/cloverage/
but for Clojurescript. It's a lot more difficult since it's compiled to JS, but in theory we have source maps and there are many JS tools to generate the report
the fact that I find nothing googling around makes me think it's not going to be easy
but that assumes the code you’re covering can be run in self-hosted, which isn’t always the case
Since you mentioned self-hosted, if I have a ClojureScript library (core.rrb-vector in particular is on my mind, since I've been doing bug fixed for it recently), is there some command or three one can run to determine whether a library supports self-hosted, and if not, what parts of the code are stopping that?
there’s not really a good way to determine that, other than to load the code and inspect the error 😕
it can often be pretty deep in your dependencies too… like a macro that calls some library that uses some library that calls a Java method
Are there instructions you know of for attempting to load a library in a self-hosted cljs environment? I doubt it is difficult -- just have never done it.
Hmm, I found and am reading through https://clojurescript.org/guides/self-hosting to see if I can learn from there.
One thing that helps with the coverage issue is to have as much code as possible in cljc files
Which means you can use cloverage as usual and you get frontend coverage for free in a way. You can get quite far with that but would be nice to get the rest
According to this Wikipedia page on the Spidermonkey JS runtime, version 1.8.5 was first released in 2011, and there have been new versions released every year. Is it a little odd that on a Mac brew install spidermonkey
installs that old version?
Sure. Just kinda weird in a sea of packages that do seem pretty up to date. I recently got a new Mac and decided to try Homebrew instead of MacPorts to see if I was missing out. That and there is a brew install clojure
for the new Clojure CLI tools, but nothing like that for MacPorts.