You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently relying on finicky regular expressions to identify and match the extra items that are displayed at the end of each option's help. These extra items are rendered in square brackets and looks like:
[default: None]
[default: (unlimited)]
[env var: COLOR_CLI8_TIME; default: no-time]
and a variety of other formats.
The problem is that the generation of these extra items are deeply embedded within Click and are impossible to fetch independently.
That's why I propose a simple refactor of the Option.get_help_record() method, and split it in two:
a new method to compute the values of these extra items
keep the original get_help_record() as-is, but dedicated to help message rendering only
I've also heard rumors of upcoming big refactors regarding help screen generation, so I propose this small, un intrusive one as a small step towards the big one.
kdeldycke
added a commit
to kdeldycke/click-extra
that referenced
this issue
May 16, 2023
I maintain Click Extra, a drop-in replacement for Click which adds colorization of the help screen.
I am currently relying on finicky regular expressions to identify and match the extra items that are displayed at the end of each option's help. These extra items are rendered in square brackets and looks like:
[default: None]
[default: (unlimited)]
[env var: COLOR_CLI8_TIME; default: no-time]
The problem is that the generation of these extra items are deeply embedded within Click and are impossible to fetch independently.
That's why I propose a simple refactor of the
Option.get_help_record()
method, and split it in two:get_help_record()
as-is, but dedicated to help message rendering onlyI have a PR that is ready at #2517.
The text was updated successfully, but these errors were encountered: