-
Notifications
You must be signed in to change notification settings - Fork 434
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
API for parse results #257
Labels
Milestone
Comments
Closed
This was referenced Feb 4, 2018
remkop
added a commit
that referenced
this issue
Feb 25, 2018
remkop
added a commit
that referenced
this issue
Mar 1, 2018
remkop
added a commit
that referenced
this issue
Mar 1, 2018
remkop
added a commit
that referenced
this issue
Mar 1, 2018
remkop
added a commit
that referenced
this issue
Mar 6, 2018
remkop
added a commit
that referenced
this issue
Mar 12, 2018
remkop
added a commit
that referenced
this issue
Mar 14, 2018
…e original String value, optionValue/positionalValue for the strongly typed values
remkop
added a commit
that referenced
this issue
Mar 14, 2018
…e original String value, optionValue/positionalValue for the strongly typed values; added test
remkop
added a commit
that referenced
this issue
Apr 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
API for querying parse results is needed.
With the explicit model API introduced with #245, a CLI may be specified programmatically. When a command line is parsed, only the
OptionSpec
andPositionalParamSpec
objects that matched some input are given a value.The parse results API needs to provide a mechanism for applications to discover which
OptionSpec
andPositionalParamSpec
objects were matched.The text was updated successfully, but these errors were encountered: