mirror of
https://github.com/clap-rs/clap
synced 2024-12-13 22:32:33 +00:00
d840d5650e
Before #2005, `Clap` was a special trait that derived all clap traits it detected were relevant (including an enum getting both `ArgEnum`, `Clap`, and `Subcommand`). Now, we have elevated `Clap`, `Args`, `Subcommand`, and `ArgEnum` to be user facing but the name `Clap` isn't very descriptive. This also helps further clarify the relationships so a crate providing an item to be `#[clap(flatten)]` or `#[clap(subcommand)]` is more likely to choose the needed trait to derive. Also, my proposed fix fo #2785 includes making `App` attributes almost exclusively for `Clap`. Clarifying the names/roles will help communicate this. For prior discussion, see #2583
19 lines
380 B
Rust
19 lines
380 B
Rust
//! How to append a postscript to the help message generated.
|
|
|
|
use clap::Parser;
|
|
|
|
/// I am a program and I do things.
|
|
///
|
|
/// Sometimes they even work.
|
|
#[derive(Parser, Debug)]
|
|
#[clap(after_help = "Beware `-d`, dragons be here")]
|
|
struct Opt {
|
|
/// Release the dragon.
|
|
#[clap(short)]
|
|
dragon: bool,
|
|
}
|
|
|
|
fn main() {
|
|
let opt = Opt::parse();
|
|
println!("{:?}", opt);
|
|
}
|