{"id":999,"date":"2022-02-01T02:04:00","date_gmt":"2022-02-01T07:04:00","guid":{"rendered":"https:\/\/www.brunerd.com\/blog\/?p=999"},"modified":"2022-02-01T02:04:02","modified_gmt":"2022-02-01T07:04:02","slug":"jpt-1-0-and-json5-rehab","status":"publish","type":"post","link":"https:\/\/www.brunerd.com\/blog\/2022\/02\/01\/jpt-1-0-and-json5-rehab\/","title":{"rendered":"jpt 1.0 and JSON5 rehab"},"content":{"rendered":"\n

JSON5<\/a> is not<\/em> JSON nor is an IETF standard but jpt 1.0 can rehabilitate it back to standards compliant JSON. Let’s take the example from its web page.<\/p>\n\n\n\n

{\n  \/\/ comments\n  unquoted: 'and you can quote me on that',\n  singleQuotes: 'I can use \"double quotes\" here',\n  lineBreaks: \"Look, Mom! \\\nNo \\\\n's!\",\n  hexadecimal: 0xdecaf,\n  leadingDecimalPoint: .8675309, andTrailing: 8675309.,\n  positiveSign: +1,\n  trailingComma: 'in objects', andIn: ['arrays',],\n  \"backwardsCompatible\": \"with JSON\",\n}<\/code><\/pre>\n\n\n\n
Now let’s send it through jpt<\/p>\n\n\n\n
% jpt json5_example.txt        \n{\n  \"unquoted\": \"and you can quote me on that\",\n  \"singleQuotes\": \"I can use \\\"double quotes\\\" here\",\n  \"lineBreaks\": \"Look, Mom! No \\\\n's!\",\n  \"hexadecimal\": 912559,\n  \"leadingDecimalPoint\": 0.8675309,\n  \"andTrailing\": 8675309,\n  \"positiveSign\": 1,\n  \"trailingComma\": \"in objects\",\n  \"andIn\": [\n    \"arrays\"\n  ],\n  \"backwardsCompatible\": \"with JSON\"\n}\n<\/code><\/pre>\n\n\n\n
That last line is a bit misleading. JSON5 texts are totally not<\/em> backward compatible with JSON parsers. What they mean is that JSON5 parsers<\/em> are backward compatible with JSON. FYI – Every single JSON5 addition is not compatible with JSON, I should know I had to write parsing rules and behaviors to deal with it! Let’s use the -c<\/code> flag to comment on all the work that went into un-junking the above example<\/p>\n\n\n\n
% jpt -c .\/json5_example.txt \n{\n  \"unquoted\": \"and you can quote me on that\",\n  \"singleQuotes\": \"I can use \\\"double quotes\\\" here\",\n  \"lineBreaks\": \"Look, Mom! No \\\\n's!\",\n  \"hexadecimal\": 912559,\n  \"leadingDecimalPoint\": 0.8675309,\n  \"andTrailing\": 8675309,\n  \"positiveSign\": 1,\n  \"trailingComma\": \"in objects\",\n  \"andIn\": [\n    \"arrays\"\n  ],\n  \"backwardsCompatible\": \"with JSON\"\n}\n--> Original error: SyntaxError: JSON Parse error: Unrecognized token '\/'\n--> Byte 5: \/\/ line comment (JSON5)\n--> Byte 19: unquoted object key name (JSON5)\n--> Byte 29: single quoted string (JSON5)\n--> Byte 63: unquoted object key name (JSON5)\n--> Byte 77: single quoted string (JSON5)\n--> Byte 113: unquoted object key name (JSON5)\n--> Byte 138: \\ escaped newline in string (JSON5)\n--> Byte 153: unquoted object key name (JSON5)\n--> Byte 164: 0x hex value (JSON5)\n--> Byte 177: unquoted object key name (JSON5)\n--> Byte 198: decimal point wihtout preceding digit (JSON5)\n--> Byte 208: unquoted object key name (JSON5)\n--> Byte 228: trailing decimal lacking mantissa (JSON5)\n--> Byte 233: unquoted object key name (JSON5)\n--> Byte 247: explicit plus + for value (JSON5)\n--> Byte 253: unquoted object key name (JSON5)\n--> Byte 268: single quoted string (JSON5)\n--> Byte 282: unquoted object key name (JSON5)\n--> Byte 290: single quoted string (JSON5)\n--> Byte 296: trailing comma (JSON5)\n--> Byte 336: trailing comma (JSON5)\n<\/code><\/pre>\n\n\n\n
Yeah there’s so much wrong with JSON5 vs JSON its not funny. It’s baffling that Apple is acknowledging it by adding JSON5 parsing to their frameworks<\/a>! At least they don’t generate it! Despite not being funny, let’s try anyway, here’s some more JSON5 example to show some of the other ways it can lead you astray.<\/p>\n\n\n\n
{\n\t\"jpt_lineBreakHandling\": \"Extended parsing to ignore tabs \\\n\tafter escaped newlines.\\nIf JSON5 is supposed to be human readable \\\n\tshouldn't tabs be included in the escaping?\",\n\t\"leadingDecimalPoint\": .8675309, \n\t\"andTrailingDecimal\": 8675309.,\n\t\"negativeLeadingDecimalPoint\": -.1234, \n\n\t\/\/Infinity converts to null, use -I for string\n\t\"+Infinity\": +Infinity,\n\t\"-Infinity\": -Infinity,\n\t\"Infinity\": Infinity,\n\t\/\/null is not a number now is it? done.\n\t\"NaN\": NaN,\n}<\/code><\/pre>\n\n\n\n
Running this through jpt we’ll get pure JSON output<\/p>\n\n\n\n
% jpt .\/json5_examples_brunerd.txt \n{\n  \"jpt_lineBreakHandling\": \"Extended parsing to ignore tabs after escaped newlines.\\nIf JSON5 is supposed to be human readable shouldn't tabs be included in the escaping?\",\n  \"leadingDecimalPoint\": 0.8675309,\n  \"andTrailingDecimal\": 8675309,\n  \"negativeLeadingDecimalPoint\": -0.1234,\n  \"+Infinity\": null,\n  \"-Infinity\": null,\n  \"Infinity\": null,\n  \"NaN\": null\n}\n\n\n#-I to convert to signed Infinity strings instead of null\n#-8 to convert NaN to string \"NaN\" (-N was taken, like NaN 8 is like Infinity but not quite :)\n% jpt -I8 .\/json5_examples_brunerd.txt \n{\n  \"jpt_lineBreakHandling\": \"Extended parsing to ignore tabs after escaped newlines.\\nIf JSON5 is supposed to be human readable shouldn't tabs be included in the escaping?\",\n  \"leadingDecimalPoint\": 0.8675309,\n  \"andTrailingDecimal\": 8675309,\n  \"negativeLeadingDecimalPoint\": -0.1234,\n  \"+Infinity\": \"+Infinity\",\n  \"-Infinity\": \"-Infinity\",\n  \"Infinity\": \"Infinity\",\n  \"NaN\": \"NaN\"\n}<\/code><\/pre>\n\n\n\n
The fact that they added the data type of +\/- Infinity and NaN really complicates the conversion since JSON doesn’t have equivalents. By default Infinity converts to null<\/code> but -I<\/code> will convert it to the string \"Infinity\"<\/code> with signedness if specified. NaN<\/code> is also converted to null by default but the -8<\/code> flag will convert it to the string \"NaN\"<\/code>. Why 8? Because it’s sort like infinity but it’s not, just like NaN.<\/p>\n\n\n\n
If you have need to rehab JSON5 back to JSON then jpt<\/a> might be able to help you out. It can run on Mac all the way back to OS X Tiger (10.4) all the way up to the newest macOS Monterey (12) and on other *nixes with jsc<\/code> installed. Check the jpt Releases<\/a> page<\/p>\n","protected":false},"excerpt":{"rendered":"
JSON5 is not JSON nor is an IETF standard but jpt 1.0 can rehabilitate it back to standards compliant JSON. Let’s take the example from its web page. Now let’s send it through jpt That last line is a bit misleading. JSON5 texts are totally not backward compatible with JSON parsers. What they mean is […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[37,51],"tags":[],"class_list":["post-999","post","type-post","status-publish","format-standard","hentry","category-jpt","category-json"],"_links":{"self":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts\/999","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/comments?post=999"}],"version-history":[{"count":12,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts\/999\/revisions"}],"predecessor-version":[{"id":1070,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts\/999\/revisions\/1070"}],"wp:attachment":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/media?parent=999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/categories?post=999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/tags?post=999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}