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

option with coerce value should not be assumed to be boolean #46

Closed
borkdude opened this issue Oct 6, 2022 · 1 comment
Closed

option with coerce value should not be assumed to be boolean #46

borkdude opened this issue Oct 6, 2022 · 1 comment

Comments

@borkdude
Copy link
Contributor

borkdude commented Oct 6, 2022

Repro:

(cli/parse-opts ["--foo"] {:coerce {:foo []}})
;;=> {:foo true}

This should be {:foo []}

cc @mk

@borkdude
Copy link
Contributor Author

borkdude commented Oct 6, 2022

The above issue can't be fixed as originally suggested, since options without values are assumed to be booleans: {:foo [true]}.

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