Line 112-113 in jsx_parser.erl breaks when you give it a tuple that is not an Erlang timestamp, for instance:
{<<"x">>, <<"y">>, []}
One solution would be to add an option "interpret_timestamps" that activates the Erlang timestamp code.
Love your work, btw.
/denonde
Line 112-113 in jsx_parser.erl breaks when you give it a tuple that is not an Erlang timestamp, for instance:
{<<"x">>, <<"y">>, []}
One solution would be to add an option "interpret_timestamps" that activates the Erlang timestamp code.
Love your work, btw.
/denonde