Helping with the Rich backlog (Bug fixes & triage focus)

[kmvanbrunt]

I want to express my appreciation for the incredible work that goes into Rich. As someone who maintains an open-source project (cmd2), I completely understand how overwhelming it can be. And that's with a user base far smaller than yours.

Since November 2024, I’ve reported four bugs, and I am very grateful that one of them has already been fixed. I wanted to briefly follow up on the remaining three:

#3577 - Trailing line break removed by Text.from_ansi()
#3948 - Table title always displays on the left when soft_wrap is True
#4028 - Failure to propagate formatting overrides via ConsoleOptions

For the first two, there are already pull requests to fix them. For #4028, I have written the fix but I am currently unable to submit the pull request as I am not a registered contributor to the repository.

Looking through the broader backlog of issues and pending PRs, I wanted to open a proactive discussion about the best way to support the library moving forward. Maintaining a project of this scale is a massive undertaking and my intention here is strictly to see how the community can help ease that burden.

It’s clear from the existing PRs that other developers and I are more than willing to write fixes and contribute. Are there specific ways we can help triage, or a preferred process for getting community fixes reviewed and merged so the core team isn't inundated?

Thank you again for your time and for building such a fantastic library.

[willmcgugan]

My projects are currently "collaborators only" while I'm traveling. As I can't keep up with AI slop. However, I can add you as a collaborator if you wish.

I'd like to point out just because a PR satisfies your (or anyone's) use case, it does not mean it is the best fix. And I can't know that until I consider the problem carefully. I'm sure you wouldn't merge anything in your projects without due consideration.

I'd also like to suggest that you aren't being inconvenienced here. These issues have straight-forward workarounds, and you can always subclass. The license even permits you to copy a renderable and modify it accordingly.

If there is something that is legitimately blocking you, without an easy workaround, you can ask a favor of me to prioritize it. I'm an agreeable guy, and likely to want to help you out.

If you want to help out with Rich, you could triage issues. Most issues aren't bugs or actionable tasks. They are tech support.

Finally, let me reassure you I will do another pass on Rich in the near future.

[kmvanbrunt]

Thank you, I'd very much appreciate it if you made me a collaborator so I can see what help I can offer.

As you point out, workarounds are possible, and we've introduced them into our code to ensure our users have a seamless experience working with Rich in the meantime.

Enjoy your travels!