cljdoc 2026-09-14

It seems like cljdoc doesn't handle "backtick x backtick" correctly. In the latest release under the https://cljdoc.org/d/polylith/clj-poly/0.3.33/doc/libraries#transitive , near the sentence "Three new rows appear". The corresponding code can be found https://github.com/polyfy/polylith/blob/3e91cbc1872c6a83ccc9f3cfb8907be964df97b7/doc/libraries.adoc?plain=1#L241.

✅ 1

I shall take a peek

👍 1

One way to address is to replace +`` with pass:[+]``

For your local/lib-a issue I referred to: https://docs.asciidoctor.org/asciidoc/latest/text/monospace/#unconstrained You have:

* `project-d` resolves `com.stuartsierra/component` to `0.1.0` and
  `com.stuartsierra/dependency` to `0.1.1`, both transitively via `brick3`'s
  `local/lib-a` - proving that the dependency tree is followed through local
  libraries too, not just Maven ones.
When you have text glued to monospace, you need to use double-ticks. So instead of brick3`'s` you need `brick3``'s`.

Let me know if that solves things for you!

For the backtick rendering, I had to refresh my brain on how asciidoc works by reading: https://docs.asciidoctor.org/asciidoc/latest/text/literal-monospace/ +foo+`` tells asciidoc to emit foo literally. You have:

Three new rows appear - `com.stuartsierra/component 0.1.0`, `com.stuartsierra/dependency
0.1.1` and `medley/medley 1.0.0` - plus a `+` for `c` on the existing
`com.stuartsierra/dependency 1.0.0` row.
A `+` means the project only gets that library+version transitively (`x` / `t` are
still used for a directly declared library, `-` for "not on the classpath"):
So you are telling asciidoc to emit everything between the opening +` and the closing +` literally:

Okay, will have a look, thanks!

An alternative to pass:[+]`` that seems to work is {plus}``.

👍 1