If we allow positional boolean parameters, then this is not only allowed, but what is generated by the dialog for a command with a single boolean param:
> foo true
Clicking on the checkbox again gives:
> foo false
Which is the same as 'foo' since all boolean params default to false. This is confusing, particularly given the following 2 synonym for 'foo true'
> foo --name
> foo -n
It seems sensible to just disallow positional boolean params, forcing use of 'foo --name' or 'foo -n'.
This won't show up if we don't ship commands that violate this rule. Move to GCLI-FUTURE
Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.
Triage. Filter on PEGASUS.