Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update readme #181

Merged
merged 1 commit into from
Oct 31, 2024
Merged

Update readme #181

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,19 +76,12 @@

### Enhancements and bug fixes

* Boolean values (`yes`,`y`,`true`,`no`,`n` and `false`) are now parsed case-insensitively.
* Fix for `Command()` UDA: `ArrayIndexError` is not thrown anymore.
* Error messages are printed with `Config.styling` and now have the same styling as help text.
* New `errorMessagePrefix` member in `Config.styling` that determines the style of "Error:" prefix in error messages. This prefix is printed in red by default.
* New checks:
* Argument is not allowed to be in multiple argument groups.
* Subcommand name can't start with `Config.namedArgPrefix` (dash `-` by default).
* For positional arguments within a command:
* There should be no gaps in indexes, e.g. `0,1,3,4` indexes are not allowed because `2` is missed.
* Indexes should be unique, e.g. `0,1,2,3,2` indexes are not allowed because `2` is repeated.
* Number of values should be fixed (i.e. minimum number of values should be the same as maximum number of values) unless it's the last positional argument.
* Required positional arguments must go before optional positional arguments.
* Optional positional arguments are now allowed if command has default subcommand.
* Functions for parsing customization (`PreValidation`, `Parse`, `Validation` and `Action`) can now return `Result` through `Result.Success` or `Result.Error` and provide error message if needed.
* Fixes for bundling of single-letter arguments.
For example, the following cases are supported for `bool b; string s;` arguments:
Expand Down