Re: JSON decode problem

As fellow monks have said, the problem here is that it is not portable json, it needs to be evalled into a javascript environment, like your browser. So if you are in perl, what can you do? Preparse it! Lines like 'ontouchstart' in window replace them with 0 (false). And whenever you see ": new Date(", just divide the number by 1000 to get a valid epoch (the extra 3 digits are microseconds, do you need them?)

#!/usr/bin/perl

$str=' publish_date: new Date(1431654084199) ' ;
$str =~ s/:\s*new Date\((\d+)\)\s*/&epoch2timestring($1)/ge;
print $str . "\n";

sub epoch2timestring{
    my ($e) = @_;
    $e=~s/.{3}$//; # eat 3 last digits
    my $result = scalar localtime($e);
    return ': "' . $result . '" '; # gmtime() ?
}
[download]

prints:

publish_date: "Fri May 15 03:41:24 2015"

Comment on Re: JSON decode problem Select or Download Code

Replies are listed 'Best First'.
Re^2: JSON decode problem by kennethk (Abbot) on Aug 05, 2016 at 15:14 UTC
Please read my node. `showParams` cannot be evalled because of syntax errors. If a data stream is emitted with syntax errors of this magnitude, the content had better be valuable the fixes you make are going to be incredibly fragile. For example, in order to clean `showParams`, you need to detect unescaped quotes and escape them. For the sample you could run `my $str = 'showParams: "{"revertType":null,"refresh":false,"checkpoint +":false,"sheetName":"","unknownParams":"zone_id=6290&ac=a9aef098062f9 +646bd1638d0c6054c7b&account_id=62&Start_Date=2016-07-27&End_Date=2016 +-08-03","layoutId":""}"'; while ($str =~ /(?<!\\)"\s\{\s("(?:(?!\}").)*)\}"/) { substr($str, $-[1], $+[1] - $-[1]) =~ s/(?=["\\])/\\/g; }` [download] but good luck maintaining that. #11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.	[reply] [d/l] [select]
Re^3: JSON decode problem by FreeBeerReekingMonk (Deacon) on Aug 11, 2016 at 21:16 UTC
Well, that is the thing everyone is pointing out. You can either write a pre-parser that fixes it into standard JSON, then read it with the JSON modules, or parsing it yourself (which could mean you will have to implement much more). From JSON#Data_portability_issues Despite the widespread belief that JSON is a strict subset of JavaScript, this is not the case. Specifically, JSON allows the Unicode line terminators U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR to appear unescaped in quoted strings, while JavaScript does not. . In "Unsupported native data types" Wikipedia specifically states for Date() that there are some de facto standards, e.g., converting from Date to String, but none universally recognized. This JSON is "weird" like that. So each line is an `identifier: thing` where thing can be: (something that must be evaluated in Javascript itself) "{"...."}" a hash "a string" false a boolean new Date(... a date Strings and booleans are json already, the others, not that much...	[reply] [d/l]
Re^4: JSON decode problem by kennethk (Abbot) on Aug 15, 2016 at 15:45 UTC
As fellow monks have said, the problem here is that it is not portable json, it needs to be evalled into a javascript environment, like your browser. This was the specific point I was replying to. It is not valid JavaScript due to unescaped quotes, and therefore you can't leverage a JavaScript interpreter. #11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.	[reply]