CommandParser unrecognised option support #602
Assignees
Labels
branch/2.1.x
Issue for a branch
for/backport
For backporting
type/enhancement
Is an enhancement request
Milestone
Comments
jvalkeal
added
type/enhancement
jvalkeal
added a commit
that referenced
this issue
Jan 7, 2023
- This commit modifies CommandParser to better track positional parameters which previously used to go there for non-recognised options. Now using relatively dump logic of just checking if first positional parameter starts with '-' which indicates it's a candidate for a new `UnrecognisedOptionException` which then would give user an error "Unrecognised option '--xxx'" for example. - Backport #601 - Backport #602 - Fixes #603 - Fixes #604
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was somewhat missed when rework from 1.x/2.0.x to 2.1.x happened. When user is defining option which doesn't exist parser adds it as positional argument(which it then kinda is) but what really should happen is that anything starting with '-' is reported as error, aka
UnrecognisedOptionException.The text was updated successfully, but these errors were encountered: