cljdoc 2019-05-17 | Slack Archive

Fork me on GitHub

Jakub Holý (HolyJak)19:05:23

Do I always need to provide version in https://cljdoc.org/d/seancorfield/next.jdbc/1.0.0-alpha13/doc/readme, isn't there some magical version like LATEST?

martinklepsch19:05:38

https://cljdoc.org/d/seancorfield/next.jdbc will bring you do the latest release https://cljdoc.org/d/seancorfield/next.jdbc/CURRENT/doc/readme will get you to a subpage in the latest release @holyjak

Jakub Holý (HolyJak)20:05:52

ah, it was CURRENT :) Is there a link to it somewhere, if I forget it again?

Jakub Holý (HolyJak)20:05:08

because https://cljdoc.org/d/seancorfield/next.jdbc/ seems to redirect to https://cljdoc.org/d/seancorfield/next.jdbc/1.0.0-alpha13/doc/readme so I dont see how to discover this "CURRENT" magic..

martinklepsch20:05:36

Do you mean if this is documented somewhere or if there are links that use CURRENT on cljdoc?

seancorfield22:05:54

This is why the cljdoc badge on https://github.com/seancorfield/next-jdbc specifically links to https://cljdoc.org/d/seancorfield/next.jdbc/CURRENT -- as a reminder to myself 🙂