Closed
Bug 926464
Opened 11 years ago
Closed 8 days ago
Manifest parser should recognize capitalized constants: skip-if = True doesn't work, skip-if = true does
Categories
(Testing :: Mozbase, defect)
Testing
Mozbase
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Gijs, Unassigned)
Details
As per summary. Especially because the moz.build documentation says you can use the constants "True", "False" and "None", and the test manifest documentation on MDN doesn't say anything, so I assumed I should use the capitalized versions and just wasted a couple of hours of try machine time and my own sanity trying to figure out what was up. </rant>
Comment 1•11 years ago
|
||
Not sure if we should actually support it, but we should error out fast
Comment 2•11 years ago
|
||
I'd support erroring better here and fixing the docs. I did document the expression syntax in the manifestparser docs: http://mozbase.readthedocs.org/en/latest/manifestdestiny.html#manifest-conditional-expressions
Comment 3•6 years ago
|
||
Mass closing bugs with no activity in 2+ years. If this bug is important to you, please re-open.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Comment 4•6 years ago
|
||
This is still a problem which needs to be fixed. The mentioned docs can now be found at: https://firefox-source-docs.mozilla.org/mozbase/manifestparser.html#manifest-conditional-expressions
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Updated•2 years ago
|
Severity: normal → S3
Comment 5•8 days ago
|
||
as we are on .toml, we do not support "True" as a valid value.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 8 days ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•