Optarg restrictions
Open
Bug
Repro Attached
- Dominant language
- Clojure
- Stars
- 1.7k
- Forks
- 178
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.