mirror of
https://github.com/clap-rs/clap
synced 2024-12-14 06:42:33 +00:00
No description
2bbb81f311
Things that tripped up a user - Derive reference was misunderstood to say that the only alternative to the built-in value parser behavior was to implement `ValueParserFactory` - We now delegate to `value_parser!`s docs any talk of integrating into it (it should have been a subbullet of "not present" anyways) - `value_parser!` relies too much on the example to demonstrate behavior when the user will likely make the determination of whether its relevant before then - We are now more upfront what type mappings are supported - Too many steps to find all information - For example, a user needs to look at `TypedValueParser` implementations, `ValueParserFactory` implementations, and `From<T> for ValueParser` implementations to understand what all can be used - We are now more upfront with a lot of this information at the entry points the user is most likely to look at In addition, I did an audit of the docs to make sure they were updated for us only supporting the new behavior and all of the new APIs. See https://www.reddit.com/r/rust/comments/xjlie4/preannouncing_clap_40_a_rust_cli_argument_parser/ip9kzf1/ |
||
---|---|---|
.github | ||
assets | ||
clap_bench | ||
clap_complete | ||
clap_complete_fig | ||
clap_derive | ||
clap_lex | ||
clap_mangen | ||
examples | ||
src | ||
tests | ||
.clippy.toml | ||
.gitignore | ||
.pre-commit-config.yaml | ||
Cargo.lock | ||
Cargo.toml | ||
CHANGELOG.md | ||
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
Create your command-line parser, with all of the bells and whistles, declaratively or procedurally.
For more details, see: