Fork me on GitHub
#cljdoc
<
2022-02-11
>
Jakub Holý (HolyJak)15:02:06

Hi! When we get import errors like https://cljdoc.org/builds/53065 >

Could not find revision v0.1.4 in repo ",
>  :data {:origin "<https://g>
wouldn't it be best to simply throw away that revision? In this case it seems http://scicloj.ml had a v0.1.4 but then removed it. As a result, https://cljdoc.org/d/scicloj/scicloj.ml/ will lead to the failed import site until a new, same or higher version is released (instead of the last actually available, v0.1.4)

lread19:02:11

@holyjak I think cljdoc search is currently driven by clojars data, and it has that revision https://clojars.org/scicloj/scicloj.ml/versions/0.1.4. But yeah, maybe when an import results in 0 articles and 0 namespaces, it should be excluded for search results, if that is what you are getting at?

Jakub Holý (HolyJak)19:02:49

That as well as what is attempted displayed at https://cljdoc.org/d/scicloj/scicloj.ml/

lread19:02:58

Right… I see what you mean. Maybe navigating to the last good import would make more sense? But… also knowing that there are later releases is also interesting to the reader.

lread22:02:03

Sounds maybe worthy of a git issue then?

👍 1
lread13:02:42

Coolio! Thanks!