Status page: Add descendants count, sort alphabetically

[jaimergp]

PR Checklist:

• note any issues closed by this PR with closing keywords
• if you are adding a new page under docs/ or community/, you have added it to the sidebar in the corresponding _sidebar.json file
• put any other relevant information below

Addressing #2137 (comment)

cc @h-vetinari

[netlify]

✅ Deploy Preview for conda-forge-previews ready!

Name	Link
🔨 Latest commit	bcde9c5
🔍 Latest deploy log	https://app.netlify.com/sites/conda-forge-previews/deploys/663b1ebb542b7c000857ace3
😎 Deploy Preview	https://deploy-preview-2176--conda-forge-previews.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jaimergp]

Ah wait, reading #2090 (comment), I think this needs to know the total number, not just the children.

Any tips @afshin?

[jaimergp]

nvm it was there right in the json payload

[beckermr]

Should this be "Number of Descendants" or something? It is clearly a number but IDK in terms of things being accessible.

[h-vetinari]

I also think we should use the same name twice (c.f. "immediate children") - either children or descendants, but not both. I mean yes, in a strictly genealogical sense the distinction makes sense, but I think it ends up being more confusing to call the same concept by two different names.

So perhaps "Total number of children" / "Immediate children"?

[beckermr]

"dependent feedstocks" is the most precise term I can think of for this. It is wordy though. :)

[jaimergp]

I was trying to save some space in the headers but yea, let me know which ones you prefer and we'll get that in. If we go for verbose, I'd pick "Total number of children" / "Immediate children".

[h-vetinari]

Thanks a lot @jaimergp for tackling this, this already looks very promising!

Could we sort by (descendants DESC, name ASC)? That's mostly how the previous status page worked, i.e. grouping the packages with the most descendants at the top.

It would be amazing if one could sort the table by a given column when clicking on the header, but I imagine that's a whole 'nother level of complexity so I'm not asking for that here.

[jaimergp]

It would be amazing if one could sort the table by a given column when clicking on the header, but I imagine that's a whole 'nother level of complexity so I'm not asking for that here.

I briefly looked into it by trying to bring the logic from the overview table, but it was a bit trickier than expected. I'll add it to the meta issue todo list.

Could we sort by (descendants DESC, name ASC)?

I implemented this sort now:

1. Total children DESC
2. Status as in ORDERED (i.e. as in the progress bar)
3. Name ASC

This way you can see the biggest chunks first, but you can still filter unwanted statuses out with the buttons above. Otherwise, you'd have to scroll the whole table for all statuses just to parse which ones are the biggest.

[jakirkham]

Thanks all! 🙏

[h-vetinari]

Thanks @jaimergp, this looks great and is really really helpful! 🙏

[h-vetinari]

I implemented this sort now:

Need to emphasise again what a huge improvement this is. Being able to sort all outstanding statuses by total children (rather than having to cross-reference between different status sections) is amazing! 🤩