Clojurians Log v2

no, we discussed this at some point but overall I felt like the alphabetical order would provide a more consistent experience for readers

i get why you want it though, maybe a namespace docstring using [[wikilinks]] could guide a user to read things in a certain order?

dang, okay

would you accept a patch to support it? or nah

I was thinking about that, but I'd like that to be a switch in the UI rather than per project if that makes sense?

i can write an md file to document these items in logical order, this just seemed the easiest way to say "these things are all in one namespace but each subset is grouped semantically"

@nbtheduke, only one other person (that I know of) has asked for this. My thought is the API docs are an index of vars that folks expect to be ordered alphabetically. My feeling is a user guide is the place to describe the semantics and groupings. That said, I do maintain a couple of projects that have kitchen sink APIs. For these, I provide a secondary index in the namespace docstring that provides the grouping you might be thinking of: • https://cljdoc.org/d/rewrite-clj/rewrite-clj/1.1.48/api/rewrite-clj.zip • https://cljdoc.org/d/etaoin/etaoin/1.1.42/api/etaoin.api This has worked for me; perhaps it could work for you too.

oh wow, is that all in the docstring? that's clever. i'll borrow that for lazytest

Yep, I maintain the ns docstring index manually, which can be a bit of a pain to remember to update, but it works well enough.

I declare a hiccup 😊

hmmm… I do see some ups and downs… will have to look into cause

It's up for me again 👍

👍

Thanks, @martinklepsch, and OpenCollective contributors! My frugally retired ass appreciates all donations and contributions! simple_smile