Replies: 1 comment
-
Personally, this feels a bit of a stretch to include such specific information when we don't interact with it (e.g. providing layered config, see #2763). However, I have been exploring the idea of a way to attach arbitrary data to arguments / commands along with making the help rendering more extensible which would allow people to implement this on their side. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
My binary uses environment variables that aren't bound by clap args but used internally via
std::env::var()
. Currently I form a custom description with all supported env variables, their respective default values etc. and pass it viaafter_help
.I wonder if it's possible or worth improvement to provide facilities for defining unbounded env variables via derive macro, for example:
Then the new "Environment variables:" section can be appended below the normal "Options" output, i.e:
Beta Was this translation helpful? Give feedback.
All reactions