cljdoc

juhoteperi 2023-06-14T13:25:42.475529Z

I pushed a new Reitit version, clicking on build just for the main package didn't trigger build for the modules so API docs is empty. Are the other modules built automatically later? I'm not sure how this has worked before.

juhoteperi 2023-06-14T13:26:47.399859Z

Now I see reitit-core job on circleci, I didn't trigger that myself at least

lread 2023-06-14T14:00:49.925769Z

Hi @juhoteperi! Here are https://github.com/cljdoc/cljdoc/blob/master/doc/userguide/for-library-authors.adoc#module-support (notice, even, the mention of Reitit!). I think I could add a few words maybe. Cljdoc will try to build docs for all jars published to clojars with no special consideration for modules (for the build aspect). So the complete docset for a library with modules will lag a bit as cljdoc builds the docs for modules.

juhoteperi 2023-06-14T14:19:33.059079Z

oh I read the first line "every 60 seconds" and then wondered why is it taking longer... next line says it is running jobs every 10 minutes

lread 2023-06-14T14:43:16.335299Z

If you want/need to have the builds trigger sooner, you can always trigger the builds yourself.

lread 2023-06-14T14:46:02.873099Z

I often do that as part of my release flow, https://github.com/clj-commons/rewrite-clj/blob/fe3d880c1ccea5724d5048d3735de859ee235515/script/ci_publish.clj#L54-L67. For Reitit, you'd have to trigger a build for each submodule jar.

juhoteperi 2023-06-09T13:01:13.029169Z

Okay I think I now found reitit-core analysis failure: https://app.circleci.com/pipelines/github/cljdoc/builder/42233/workflows/dc9220f7-a836-4013-a9f2-06600e097b6b/jobs/58608

juhoteperi 2023-06-09T13:07:04.258649Z

Aha it was repl code in a namespace what wasn't correctly commented and is already removed in master

lread 2023-06-09T13:27:38.632919Z

Hi @juhoteperi! All good? Or is there something you'd like me to look into on the cljdoc side?

juhoteperi 2023-06-09T14:01:02.628229Z

Yeah I found the reason. Due to Reitit multimodule setup it just took a while to find the correct place for the logs.

juhoteperi 2023-06-09T14:03:50.228959Z

I might add the check github action to catch these cases earlier

lread 2023-06-09T14:05:17.725499Z

Coolio, glad you are sorted out. It's on my todo list to freshen up the github check action, but not sure when I'll get to it.

juhoteperi 2023-06-09T14:05:34.209359Z

And hmm, does cljdoc always default to the latest version even if that is a alpha?

lread 2023-06-09T14:06:59.929869Z

Yeah, think so, are you seeing something different?

juhoteperi 2023-06-09T14:07:25.258989Z

No but I was wondering it could be safer to show the latest non-alpha & non-snapshot

juhoteperi 2023-06-09T14:07:35.782909Z

Or link to both from our readme

lread 2023-06-09T14:07:45.077969Z

snapshots are treated differently

lread 2023-06-09T14:09:20.733419Z

But I think cljdoc doesn't currently categorize beyond snapshot non-snapshot.

lread 2023-06-09T14:14:51.489349Z

Interesting idea to explore though. Feel free to raise an issue.