Fork me on GitHub
#cljdoc
<
2019-04-23
>
martinklepsch00:04:58

@seancorfield fyi you can also link to the latest version with a much shorter link like this: https://cljdoc.org/d/seancorfield/next.jdbc

martinklepsch00:04:14

This will automatically redirect to the first article at the latest RELEASE version

seancorfield02:04:03

Yeah, but that doesn't show up in the browser address bar for easy copy'n'pasting πŸ™‚

martinklepsch03:04:27

That's true, just wanted to mention it in case the long links bothered you πŸ˜„

seancorfield20:04:10

@martinklepsch Why does this URL show the Alpha 9 readme? https://cljdoc.org/d/seancorfield/next.jdbc/1.0.0-alpha5/doc/readme - it doesn't! But the readme includes badges that are dynamic and therefore confusingly show the current version 😐

seancorfield20:04:11

I guess I'll have to add text to the README to make that less confusing... Does anyone run into this? Or have suggestions to make it less confusing?

martinklepsch20:04:09

Happy to consider ideas to make this less confusing - we can do whatever with the articles. We could just remove the badge if it’s there but not sure if that’s such a great idea

dominicm20:04:38

ifdef::env-github[]
image::
endif::[]

martinklepsch21:04:29

Oh right, Asciidoc already has a solution

dominicm21:04:52

The natural solution is always to rewrite everything in adoc

polymeris21:04:22

would it be less confusing if the badge just said "cljdoc" without the version number?

martinklepsch21:04:54

right that may also be an option, given that it generally links to the latest version anyways

seancorfield21:04:43

For now, I changed my README to say

The latest versions on Clojars and on cljdoc:

<<badges go here>>

This documentation is for 1.0.0-alpha9.
Since I do a find&replace for the version number everywhere in the project before I build each release, this will work for now (well, whenever I get around to cutting the next release it will start working on cljdoc πŸ™‚ )

martinklepsch21:04:45

cool πŸ™‚ asciidoc is pretty nice on cljdoc as well, just FYI: https://cljdoc.org/d/nrepl/nrepl/0.6.0/doc/usage/server

seancorfield21:04:46

But it's fairly common for project READMEs to contain the Clojars badge (and possibly other version-specific dynamic badges) so I think some sort of rewriting is going to be needed ...

seancorfield21:04:21

Does GitHub know how to render a README written in AsciiDoc?

martinklepsch21:04:56

just click the github link in the top right corner of the nrepl docs and you can see what that looks like (or the edit on github link at the end of the page I linked)

seancorfield21:04:25

OK, maybe I will do that then (it'll make me learn it at long last πŸ™‚ )

seancorfield21:04:26

nREPL's README is markdown, not adoc, BTW.

πŸ™ˆ 4
martinklepsch22:04:00

The callouts with tips, warnings and all that are super nice