Skip to content

CommandParser unrecognised option support #602

Closed
@jvalkeal

Description

@jvalkeal

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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions