Skip to content

Optarg restrictions #615

Open
Open
@martinklepsch

Description

@martinklepsch

Via Slack:

Hey. I've just wasted another hour and a half debugging WTH boot could not parse my string argument. Long story short, turned out that my arg definition:

[i input S3PATH str "blablabla"]

creates a parse function that turns the provided string into a vector, and then the verifier fails.
Turns out the 3 in S3PATH was to blame.
Nowhere in the documentation I could not find any mention that digits in the optarg name change > the parser behavior.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions