-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
requiring a value be supplied for an option #52
Comments
Yes, but we should only require something after |
I'd say this should fail with a required error: user=> (cli/parse-opts ["--foo"] {:coerce {:foo :number}})
{:foo true} and this should not, as booleans may just be the flag: user=> (cli/parse-opts ["--foo"] {:coerce {:foo :boolean}})
{:foo true} |
Yeah, this looks right to me |
OK, I'm working on it |
borkdude
added a commit
that referenced
this issue
Dec 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
clojure.tools.cli gives you a way to specify that a value must be supplied for an option by specifying the option with something like
If your args include
--entry
but nothing after, it's treated as an error. Would it be possible to do something similar with this library?:require
mandates the presence of an option, but doesn't handle the case where no value is supplied.The text was updated successfully, but these errors were encountered: