671837 - GCLI should not allow boolean parameters to be positional

Status: RESOLVED FIXED

(DevTools :: Console, defect, P2)

Description

[Joe Walker [:jwalker]]

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'.

Comment 1

[Joe Walker [:jwalker]]

This won't show up if we don't ship commands that violate this rule. Move to GCLI-FUTURE

Comment 2

[Joe Walker [:jwalker]]

Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.

Comment 3

[Joe Walker [:jwalker]]

Triage. Filter on PEGASUS.

Comment 4

[Joe Walker [:jwalker]]

Triage. Filter on PEGASUS.

Comment 5

[Joe Walker [:jwalker]]

GCLI Triage.

Comment 6

[Joe Walker [:jwalker]]

Triage.