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.

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

type check in ArgumentParser.Done() or before #11

Open
jsc86 opened this issue Dec 20, 2018 · 0 comments
Open

type check in ArgumentParser.Done() or before #11

jsc86 opened this issue Dec 20, 2018 · 0 comments
Labels
enhancement New feature or request prio-medium

Comments

@jsc86
Copy link
Owner

jsc86 commented Dec 20, 2018

If the content of a presumed command line argument does not fit the value type of assumed argument specification, there is not explicit type checking at all. Access fails late by implicit type checking, when the value is accessed (via ParserResult or rule checks) or mapped (ParserResultMapper/ParserResultConfigBackend). It should fail early and/or handled gracefully by not assuming it to be the expected argument in CommandLineParser.Parse. CommandLineParser.Match/Argument.Done would likely be the right place for graceful handling.

@jsc86 jsc86 added the enhancement New feature or request label Dec 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request prio-medium
Projects
None yet
Development

No branches or pull requests

1 participant