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

Should support --opt=val, obviously, not (just) the unusual --opt val... #6

Closed
xparq opened this issue Jan 26, 2023 · 0 comments
Closed

Comments

@xparq
Copy link
Owner

xparq commented Jan 26, 2023

Fortunately, at least the entire --opt=val string is captured. (But remember --opt=val1,val2,val3, or perhaps even --opt=v1, v2, v3, or even --val="a b c", v2,v3!...)

xparq pushed a commit that referenced this issue Jan 27, 2023
Kept the `--long val` format, too. That even supports multival!
Renamed unnamed() to positional().
Class publics moved near the top for better UX.
Test improvements. (Now all should pass.)
xparq pushed a commit that referenced this issue Jan 27, 2023
Kept the `--long val` format, too. That even supports multival!
Renamed unnamed() to positional().
Class publics moved near the top for better UX.
Test improvements. (Now all should pass.)
xparq pushed a commit that referenced this issue Jan 27, 2023
Kept the `--long val` format, too. That even supports multival!
Renamed unnamed() to positional().
Class publics moved near the top for better UX.
Test improvements. (Now all should pass.)
@xparq xparq closed this as completed Jan 27, 2023
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

No branches or pull requests

1 participant