Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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/
- Loading branch information
Showing
5 changed files
with
44 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters