You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have a config like { boolean: ["foo"], string: ["foo"] }, I expect that passing --foo (without any values) to return true in the parsed object. Below shows the exact scenario:
When I have a config like
{ boolean: ["foo"], string: ["foo"] }
, I expect that passing--foo
(without any values) to returntrue
in the parsed object. Below shows the exact scenario:It's not documented that both boolean and string would work, but it seems to almost work as expected to me with the first case that should be
true
.As a workaround, I'm doing something like this:
Related: changesets/changesets#1392
The text was updated successfully, but these errors were encountered: