Closed
Bug 659268
Opened 13 years ago
Closed 8 years ago
GCLI command parameters could use more advanced validation. Experiment.
Categories
(DevTools Graveyard :: Graphic Commandline and Toolbar, defect)
DevTools Graveyard
Graphic Commandline and Toolbar
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: jwalker, Unassigned)
Details
Sometimes parameters need specific validation which can't be performed by the type system. $ example --verbose --quiet Another example could be resource names which are un-enumerable, and yet validatable. If would be nice if we could add custom validation to be performed by the command line before the command is invoked for real.
Reporter | ||
Updated•13 years ago
|
Blocks: GCLI-EXPERIMENT
Reporter | ||
Comment 1•13 years ago
|
||
See also https://github.com/joewalker/gcli/issues/6
Reporter | ||
Comment 2•13 years ago
|
||
The given example "--verbose --quiet" isn't great because we might be able to do better with "--output [verbose|quiet|default]" or similar. This observation does not invalidate this bug however - there are times when more complex validation is needed. The observation does point out that there are times when we can alter the command syntax to provide the same results without needing to write extra code.
Reporter | ||
Comment 4•13 years ago
|
||
Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.
Component: Developer Tools → Developer Tools: Console
Reporter | ||
Updated•12 years ago
|
No longer blocks: GCLI-FUTURE
Reporter | ||
Updated•12 years ago
|
Target Milestone: --- → Firefox 17
Comment 7•12 years ago
|
||
One more case where validation would be required: screenshot command has 2 options 'chrome' and 'selector' chrome enables chrome screenshot capturing rather than content; And selector lets us choose a node via its unique selector (#id.class) when you do simply >> screenshot --selector h1.img it takes screnshot of the image that is h1 but when you try to do the following: >> screenshot --chrome --selector h1.img the context of the selector should now be switched to chrome, so that I could do this: >> screenshot --chrome --selector #webConsole where #webConsole is a XUL element. but right now what happens is that 'selector' option still tries to find the node in content context and there is no way to get the selector to match a chrome/XUL node.
Reporter | ||
Comment 8•12 years ago
|
||
New component triage. Filter on "Lobster Thermidor aux crevettes with a Mornay sauce"
Component: Developer Tools: Console → Developer Tools: Graphic Commandline and Toolbar
Reporter | ||
Comment 9•10 years ago
|
||
Resetting priorities because these P* levels are very out of date. Sorry for the bug spam. Filter on Lobster Thermidor
Priority: P3 → --
Reporter | ||
Comment 10•8 years ago
|
||
Triage. Filter on Lobster Thermidor. Nice idea, but no need to keep on file.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•6 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•