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
--arg can kinda still set to empy, albeit it's semantics is a predicate (bool), not "set to empty"!... It's "emptiness" just means [] returns true, but () still returns ""...
But... Even though the override logic should be fixed here (#16!), it's still up to the app, actually, to decide what to do with (arg) == "" or [app] == false, or any other values!
Clean up the semantics!,,, It could be equally unexpected to some/in some cases to set --thing= but have [thing] as false!
The text was updated successfully, but these errors were encountered:
The use case is repeating
arg
with--arg
to override any prev. settings.--arg
can kinda still set to empy, albeit it's semantics is a predicate (bool), not "set to empty"!... It's "emptiness" just means [] returns true, but () still returns ""...But... Even though the override logic should be fixed here (#16!), it's still up to the app, actually, to decide what to do with
(arg) == ""
or[app] == false
, or any other values!--thing=
but have[thing]
as false!The text was updated successfully, but these errors were encountered: