Allow arbitrary renderables in the descriptions and epilog #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PR #90 changed the internals of `RichHelpFormatter` to use low level rendering. This lifted some of the restrictions on what can be rendered without sacrificing parity with the argparse formatters. This PR officially adds support for arbitrary renderables as descriptions (both parser and groups description) and epilog. Co-authored-by: Mosquito <[email protected]>
hamdanal
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR #90 changed the internals of
RichHelpFormatterto use low level rendering. This lifted some of the restrictions on what can be rendered without sacrificing parity with the argparse formatters.This PR officially adds support for arbitrary renderables as descriptions (both parser and groups description) and epilog.