clap/clap_complete_fig/examples/fig_completion.rs

use clap::App;
use clap_complete::generate;
use clap_complete_fig::Fig;
use std::io;

fn main() {
    let mut app = App::new("myapp")
        .subcommand(App::new("test").subcommand(App::new("config")))
        .subcommand(App::new("hello"));

    generate(Fig, &mut app, "myapp", &mut io::stdout());
}
Refactored fig generation code to crate 2021-10-08 00:54:14 +00:00			`use clap::App;`
fix(complete): Give crates more specific names `clap_generate` originally intended to be "generate anything". With `fig`, we already broke one part out. With #3174's man support, we are also looking at keeping it separate: - More freedom to iterate on the API - Uniqueness (and potential weight) of its dependencies - man generation is normally more for distribution while completions are a mix of being distributed with the app or the app generating the completions (which will be exacerbated if we move most completion parsing logic to be in Rust) So `clap_generate` is having a lot more limited of a role than the original name conveys. I worry the generic name will be a hindrance to people discovering and using it (yes, documentation can help but there are limits). I hesitated because we are on the verge of releasing 3.0. However, doing it even later will be even more disruptive because more people will be using it (crates.io lists ~70 people using `clap_generate`). To ease things, we are still releasing `clap_generate` as a wrapper around `clap_complete`. 2021-12-31 17:59:15 +00:00			`use clap_complete::generate;`
			`use clap_complete_fig::Fig;`
Refactored fig generation code to crate 2021-10-08 00:54:14 +00:00			`use std::io;`

			`fn main() {`
			`let mut app = App::new("myapp")`
			`.subcommand(App::new("test").subcommand(App::new("config")))`
			`.subcommand(App::new("hello"));`

fix(fig): Get compiling 2021-10-12 12:57:26 +00:00			`generate(Fig, &mut app, "myapp", &mut io::stdout());`
Refactored fig generation code to crate 2021-10-08 00:54:14 +00:00			`}`