mirror of
https://github.com/clap-rs/clap
synced 2024-12-13 14:22:34 +00:00
No description
8505c47e2e
* fix(validate): Consistent conflict behavior We had two different implementations of conflicts - Validating conflicts - Allowing conflicts to override `required` - Missing members of a group conflicting with each other - Missing symmetric conflicts (A conflicts with B so B conflicts with A) This consolidates their implementations which should fix overriding of `required`. * fix(validate): Overrides always ignore required Before, if two arguments were required *and* overrode each other, then `cmd --opt=1 --other=2` succeded but `cmd --other=2` failed despite ignoring `--opt=1`. Requiring `--opt=1` to be present but unavailable doesn't help anyone and makes the behavior less predictable. Now both commands will have the same behavior. * refactor(parser): Pull out long-help determination This isn't a parser policy but command-level policy. * refactor(help): Make bool's meaning clearer * refactor(help): Consolidate help errors * refactor(help): Move help writing down a layer * refactor(parser): Parser is solely responsible for populating ArgMatches * refactor(validator): Decouple parser |
||
---|---|---|
.github | ||
assets | ||
benches | ||
clap_complete | ||
clap_complete_fig | ||
clap_derive | ||
clap_lex | ||
clap_mangen | ||
docs | ||
examples | ||
src | ||
tests | ||
.clippy.toml | ||
.gitignore | ||
.pre-commit-config.yaml | ||
Cargo.toml | ||
CHANGELOG.md | ||
clap.schema.json | ||
committed.toml | ||
CONTRIBUTING.md | ||
LICENSE-APACHE | ||
LICENSE-MIT | ||
Makefile | ||
README.md | ||
release.toml | ||
typos.toml |
clap
Command Line Argument Parser for Rust
Dual-licensed under Apache 2.0 or MIT.
- About
- Tutorial: Builder API, Derive API
- Examples
- API Reference
- CHANGELOG
- FAQ
- Questions & Discussions
- Contributing
- Sponsors
About
Create your command-line parser, with all of the bells and whistles, declaratively or procedurally.
Example
This uses our
Derive API
which provides access to the Builder API as attributes on a struct
:
use clap::Parser;
/// Simple program to greet a person
#[derive(Parser, Debug)]
#[clap(author, version, about, long_about = None)]
struct Args {
/// Name of the person to greet
#[clap(short, long)]
name: String,
/// Number of times to greet
#[clap(short, long, default_value_t = 1)]
count: u8,
}
fn main() {
let args = Args::parse();
for _ in 0..args.count {
println!("Hello {}!", args.name)
}
}
Add this to Cargo.toml
:
[dependencies]
clap = { version = "3.1.10", features = ["derive"] }
$ demo --help
clap [..]
Simple program to greet a person
USAGE:
demo[EXE] [OPTIONS] --name <NAME>
OPTIONS:
-c, --count <COUNT> Number of times to greet [default: 1]
-h, --help Print help information
-n, --name <NAME> Name of the person to greet
-V, --version Print version information
(version number and .exe
extension on windows replaced by placeholders)
Aspirations
- Out of the box, users get a polished CLI experience
- Including common argument behavior, help generation, suggested fixes for users, colored output, shell completions, etc
- Flexible enough to port your existing CLI interface
- However, we won't necessarily streamline support for each use case
- Reasonable parse performance
- Resilient maintainership, including
- Willing to break compatibility rather than batching up breaking changes in large releases
- Leverage feature flags to keep to one active branch
- Being under WG-CLI to increase the bus factor
- We follow semver and will wait about 6-9 months between major breaking changes
- We will support the last two minor Rust releases (MSRV, currently 1.54.0)
While these aspirations can be at odds with fast build times and low binary size, we will still strive to keep these reasonable for the flexibility you get. Check out the argparse-benchmarks for CLI parsers optimized for other use cases.
Selecting an API
Why use the declarative Derive API:
- Easier to read, write, and modify
- Easier to keep the argument declaration and reading of argument in sync
- Easier to reuse, e.g. clap-verbosity-flag
Why use the procedural Builder API:
- Faster compile times if you aren't already using other procedural macros
- More flexible, e.g. you can look up how many times an argument showed up, what its values were, and what were the indexes of those values. The Derive API can only report presence, number of occurrences, or values but no indices or combinations of data.
Related Projects
- wild for supporting wildcards (
*
) on Windows like you do Linux - argfile for loading additional arguments from a file (aka response files)
- shadow-rs for generating
Command::long_version
- clap_lex for a lighter-weight, battle-tested CLI parser
- clap_mangen for generating man page source (roff)
- clap_complete for shell completion support
- clap-verbosity-flag
- clap-cargo
- concolor-clap
- Command-line Apps for Rust book
trycmd
: Snapshot testing- Or for more control,
assert_cmd
andassert_fs
- Or for more control,
Feature Flags
Default Features
- std: Not Currently Used. Placeholder for supporting
no_std
environments in a backwards compatible manner. - color: Turns on colored error messages.
- suggestions: Turns on the
Did you mean '--myoption'?
feature for when users make typos.
Optional features
- derive: Enables the custom derive (i.e.
#[derive(Parser)]
). Without this you must use one of the other methods of creating aclap
CLI listed above. - cargo: Turns on macros that read values from
CARGO_*
environment variables. - env: Turns on the usage of environment variables during parsing.
- regex: Enables regex validators.
- unicode: Turns on support for unicode characters (including emoji) in arguments and help messages.
- wrap_help: Turns on the help text wrapping feature, based on the terminal size.
Experimental features
Warning: These may contain breaking changes between minor releases.
- unstable-replace: Enable
Command::replace
- unstable-multicall: Enable
Command::multicall
- unstable-grouped: Enable
ArgMatches::grouped_values_of
- unstable-v4: Preview features which will be stable on the v4.0 release