Example.json illegally starts with BOM
Closed this issue · 2 comments
Deleted user commented
The example.json file shown on the web page and used in the tests is not valid JSON. It starts with a BOM, which the JSON RFC explicitly forbids (see https://tools.ietf.org/html/rfc7159#section-8.1).
bhollis commented
Good point. It's not perfectly valid, but I've run across enough documents that do have a BOM that I wanted to make sure the add on wouldn't barf on them so it's in the example.
…-Ben
On Jan 31, 2017, at 12:57 PM, KNIME ***@***.***> wrote:
The example.json file shown on the web page and used in the tests is not valid JSON. It starts with a BOM, which the JSON RFC explicitly forbids (see https://tools.ietf.org/html/rfc7159#section-8.1).
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Deleted user commented
The problem is that some of our users used your example file with our software and then claimed our software is faulty because it correctly refused to parse the file (the Jackson library for a matter of fact). This caused several hours of debugging on our end just to find out the input was garbage.