Command `short_help` is ignored about rich-click

[aazuspan]

Yeah, defaulting to longer help strings seems totally reasonable with the improved readability from rich-click. Having a config option to preserve native click truncating might be nice if someone really needs identical behavior, but as long as you can manually override the automatic truncation using short_help, it doesn't seem like a big deal to me.

[aazuspan]

Works perfectly. Thanks again @ewels!

[ewels]

Published in v1.2.1 https://pypi.org/project/rich-click/1.2.1/

[ewels]

Thanks for reporting this - I noticed the short_help argument out of the corner of my eye a little while ago and meant to check to see if it was used but then forgot about it. We should definitely use that if supplied 👍🏻

Regarding the second bit about truncating after the first sentence (.). This was a mostly deliberate choice, as generally the wider terminal output and nicer formatting should allow longer strings for rich-click than for native click. I can see how the change in behaviour could cause issues though. I'm inclined to say that we either do nothing about this, or add a new option to take the option/arg short text from the click functions (so truncating exactly as with native). What do you think?

[ewels]

Ok, short_help should now be supported (in an almost suspiciously small amount of additional code..)

[ewels]

Ok, and added a USE_CLICK_SHORT_HELP global which uses the default click handling for commands. Setting this to True will then do the stuff with the first sentence and adding ellipses etc. as with vanilla click.

Thanks for reporting!