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

Update command line parser argument style detection, add tests. #1785

Merged
merged 3 commits into from
May 25, 2022

Conversation

cmnbroad
Copy link
Contributor

@cmnbroad cmnbroad commented Mar 15, 2022

Fixes #1784 (along with an incidental issue uncovered by that ticket).

Edit: Its worth noting that in addition to improving the error reporting in the case of an ambiguity (a putative mix of legacy and posix), this PR also changes the default i from "legacy" to "posix" for that case. See inline comments for more detail.

@cmnbroad cmnbroad marked this pull request as ready for review March 21, 2022 13:21
@mjhipp
Copy link
Contributor

mjhipp commented May 18, 2022

Any updates on this? We also have a use case where we need to use a quoted string with an = along with the new CLI syntax

Copy link
Contributor

@gbggrant gbggrant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@clintval
Copy link

clintval commented May 25, 2022

@cmnbroad @gbggrant would you be willing to merge so we can rely on this patch? Thank-you! We hit this issue with = characters in URIs when using the URI param of CreateSequenceDictionary.

@gbggrant gbggrant merged commit 923403d into master May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

mixed command line argument syntax throws too unspecific error message
4 participants