jonny (good kind) on Nostr: i don't mean to be hating, i just thought it was sorta funny how isort is yno a ...

i don't mean to be hating, i just thought it was sorta funny how isort is yno a sorting package but the order of the config docs is effectively random to me ;)

Don't mind me, but if you're asking for specific suggestions, i would love to have a description of the default sorting behavior, ideally on the homepage of the docs, because I tried to read through the docs and spent maybe ~20 minutes reading the source and i couldn't really find a succinct explanation of the default sorting behavior so i just mimicked it from vibes and what i know it does from having seen it do it.

Re: the docs design, the ToC in the pic is sorta overwhelming to me, so what I would do is remove the "Example isort.cfg" and "Example pyproject.toml" from the ToC by choking up on the max toctree depth param (i think that should do it? but idk this theme), and group them into a more manageable/explorable set of categories. I don't know isort well at all, but just skimming eg. the "known {x}" options could all get combined under "sections." It also looks like some natural categories would be "formatting" (line length, wrap length), "sorting" (even though the whole thing is sorting..., length sort, order_by_type, ), "runtime" (virtual env, extensions) and so on.