Clojurians Log v2
cljdoc
@seancorfield expectations build is running now (clj only for now) https://cljdoc.org/d/com.github.seancorfield/expectations/2.0.0-alpha2/doc/readme
@mrkiouak I also don’t have a good answer to why recur isn’t working there. Could you extend the test suite here and then maybe someone can take a look? https://github.com/cljdoc/cljdoc-analyzer/blob/a8334e4405c3f5657a981ab5189db0038ecd034a/test/integration/cljdoc_analyzer/cljdoc_main_shell_test.clj#L156
Will take a look at this. In parallel, is https://github.com/protojure/lib/blob/master/src/protojure/internal/grpc/codec/io.clj#L5 the appropriate metadata to have added to try to prevent this file from being scanned? the most recent scan https://app.circleci.com/pipelines/github/cljdoc/builder/20050/workflows/d1b47500-b9e5-40e7-bb42-dc1cdf994953/jobs/36425 with this metadata annotation seems to have had no effect...
Unfortunately the metadata does not prevent the file from being required so it still has to be possible to load it
Thank you, @martinklepsch — what was the resolution here?
Not running cljs analysis :)
Not the best of solutions but best I can offer for now :)
I mean, is it hardcoded or does it just try, fail, and ignore?
It’s hardcoded
Thank you. And “sorry” 🙂
We should fail separately but that’s kind of a long standing improvement
You’re welcome! Eager to support people making such exemplary use of cljdoc
Hi friends! I had a build that failed (https://cljdoc.org/builds/45381). I’ve fixed the reason that it failed. How do I re-run it?
There’s a hidden rebuild button in the top right (left of the GitHub link)
ah. so there is! (… edits HTML in browser …)
> Everything is looking splendid! Thanks @martinklepsch 🙂
you’re welcome 🙂