The default bug view has changed. See this FAQ.

GCLI should not allow boolean parameters to be positional

RESOLVED FIXED in Firefox 17

Status

()

Firefox
Developer Tools: Console
P2
normal
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: jwalker, Unassigned)

Tracking

Trunk
Firefox 17
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

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'.
Blocks: 659059
This won't show up if we don't ship commands that violate this rule. Move to GCLI-FUTURE
Blocks: 659052
No longer blocks: 659059
Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.
Component: Developer Tools → Developer Tools: Console
Triage. Filter on PEGASUS.
Priority: -- → P2
Triage. Filter on PEGASUS.
No longer blocks: 659052
Target Milestone: --- → Firefox 14
GCLI Triage.
Target Milestone: Firefox 14 → Firefox 16
Target Milestone: Firefox 16 → Firefox 17
Triage.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.