Closed
Bug 710177
Opened 13 years ago
Closed 6 years ago
JSON doc for stringify needs fixing
Categories
(Tamarin Graveyard :: Library, defect)
Tamarin Graveyard
Library
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pnkfelix, Unassigned)
References
Details
Lars noted that in JSON.as, the doc block above stringify is odd, it talks about "parsing", but stringify does not parse. (Words like "serialize" or "marshal" would be more appropriate and probably better english than alternatives like "unparse" or "stringify") Also, the text says: "your transformed or filtered value for each pair, rather than the default parsing, is returned in the <code>parse()</code> function output"; but by their very nature, filtered values are not part of the output.
Reporter | ||
Comment 1•13 years ago
|
||
(should take care of Bug 702551 first so that we don't get merge conflicts)
Depends on: 702551
Reporter | ||
Updated•13 years ago
|
Assignee: nobody → fklockii
Reporter | ||
Updated•12 years ago
|
Whiteboard: integration-pain-point
Reporter | ||
Updated•12 years ago
|
Whiteboard: integration-pain-point
Reporter | ||
Comment 2•12 years ago
|
||
After Bug 702551 landed, I noticed this odd sentence: When the argument passed to the <code>space</code> parameter is not a String or a Number, it is converted to a String. This string serves as the gap in the output. ECMA-262 requires the gap to be an empty string. This is poor phrasing at best; ECMA-262 does not *require* gap to be an empty string. I suspect the author meant to say something like "ECMA-262 *defaults* the gap to the empty string", or similar.
Comment 4•6 years ago
|
||
Tamarin is a dead project now. Mass WONTFIX.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Comment 5•6 years ago
|
||
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
You need to log in
before you can comment on or make changes to this bug.
Description
•