clap/tests/derive_ui/external_subcommand_misuse.rs

use clap::Parser;

#[derive(Parser, Debug)]
struct Opt {
    #[command(external_subcommand)]
    field: String,
}

fn main() {
    let _ = Opt::parse();
}
fix(derive)!: Rename `Clap` to `Parser`. 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 2021-07-13 17:50:55 +00:00			`use clap::Parser;`
Fix ui tests 2020-05-01 16:50:52 +00:00
fix(derive)!: Rename `Clap` to `Parser`. 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 2021-07-13 17:50:55 +00:00			`#[derive(Parser, Debug)]`
Fix ui tests 2020-05-01 16:50:52 +00:00			`struct Opt {`
refactor(test): Update UI tests to new attributes 2022-09-02 19:20:39 +00:00			`#[command(external_subcommand)]`
Fix ui tests 2020-05-01 16:50:52 +00:00			`field: String,`
			`}`

			`fn main() {`
			`let _ = Opt::parse();`
			`}`