This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-27
Channels
- # aws (7)
- # babashka (145)
- # beginners (83)
- # calva (18)
- # cider (11)
- # clara (9)
- # clj-kondo (59)
- # cljdoc (4)
- # cljs-dev (4)
- # cljsrn (11)
- # clojure (168)
- # clojure-australia (21)
- # clojure-dev (5)
- # clojure-europe (46)
- # clojure-italy (3)
- # clojure-nl (10)
- # clojure-taiwan (1)
- # clojure-uk (55)
- # clojurescript (85)
- # clojureverse-ops (1)
- # code-reviews (3)
- # conjure (22)
- # cursive (3)
- # datahike (3)
- # datomic (4)
- # emacs (5)
- # helix (20)
- # jackdaw (1)
- # jobs (2)
- # jobs-discuss (7)
- # lsp (1)
- # malli (5)
- # off-topic (85)
- # other-languages (4)
- # practicalli (4)
- # reitit (2)
- # releases (2)
- # sci (62)
- # shadow-cljs (181)
- # testing (5)
- # tools-deps (15)
- # xtdb (31)
What is the simplest wayt to check that my project, as a source code on my disk, would not break cljdoc analysis? F.ex. I could run on my CI to verify new changes do not suddenly break it? 🙏
@holyjak there is https://github.com/cljdoc/cljdoc/blob/master/doc/userguide/for-library-authors.adoc#configuring-articles. But I think you are more thinking of the full analysis step. I suppose you could run cljdoc-analyzer on a jar locally deployed on CI and then check the result…
> I suppose you could run cljdoc-analyzer on a jar locally deployed on CI and then check the result… That’s actually a pretty cool idea! Just having the confidence that the docs build when you publish would be great!
We could probably package this as a GitHub action/docker container pretty easily