This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-23
Channels
- # aleph (1)
- # architecture (4)
- # aws (7)
- # beginners (249)
- # boot (17)
- # calva (4)
- # cider (30)
- # cljdoc (7)
- # cljs-dev (1)
- # cljs-experience (3)
- # clojure (69)
- # clojure-dev (7)
- # clojure-europe (1)
- # clojure-italy (7)
- # clojure-japan (15)
- # clojure-spec (6)
- # clojure-uk (39)
- # clojurescript (51)
- # cursive (31)
- # data-science (4)
- # datavis (1)
- # datomic (40)
- # dirac (67)
- # duct (8)
- # editors (15)
- # emacs (9)
- # events (3)
- # figwheel-main (2)
- # fulcro (157)
- # juxt (4)
- # kaocha (11)
- # lein-figwheel (1)
- # off-topic (31)
- # pathom (18)
- # re-frame (4)
- # reagent (2)
- # reitit (16)
- # remote-jobs (1)
- # shadow-cljs (11)
- # specter (2)
- # speculative (1)
- # tools-deps (27)
- # vim (1)
- # yada (2)
Howdy there! I just tried building documentation for [metasoarous/oz "1.5.0"]
but forgot to push my repo to GitHub before running the cljdoc build, and so the README was not imported. Is there a way to get this to rebuild?
Also, witnessing this rather bizarre issue where cljdoc thinks that 1.4.0 is the newer version of the library; Any idea why this might be happening?
I guess I found an answer to the first issue here: https://github.com/cljdoc/cljdoc/blob/master/doc/userguide/faq.md#how-to-update-documentation
Hey @metasoarous 👋 There is a small hidden rebuild button in the top right (left of the GitHub/SCM link) that would have helped in this situation.
LOL; Love it. Thank you!
The reason 1.4.0 is shown as newer in this case is that versions without any non-API metadata (i.e. SCM stuff) aren't taken into account when determining the list of available versions. This could be considered a bug and if you want to open a ticket for it that would be welcome 👍
Docs for 1.5.0 are now available: https://cljdoc.org/d/metasoarous/oz/1.5.0 and if you want to add a badge to your README you can use this markdown bit:
[![cljdoc badge]()]()