Some insight about Json parser.

[coconParticipant]

{ "One": "1", "Two": "2", "Three": "3", "Four": "4", }

1 2 3 4 5 6

{ "One": "1", "Two": "2", "Three": "3", "Four": "4", }

I try to parse a JSON file like in this format above. With some debugging help, I see that the json parser can’t return a JsonObject , although the file is found and the content is loaded.

After trying lots of hours with this silly mistake I found that the very last comma (at the “Four” line) is not needed.

However here is the catch, my experience with web development says that trailing commas are allowed in Javascript but they are not allowed in the specification. http://www.json.org/

JavaScript

var json = { "One": 1, "Two": 2, "Three": 3, }; undefined json Object {One: 1, Two: 2, Three: 3}One: 1Three: 3Two: 2__proto__: Object

1 2 3 4 5 6 7 8

var json = {     "One": 1,     "Two": 2,     "Three": 3, }; undefined json Object {One: 1, Two: 2, Three: 3}One: 1Three: 3Two: 2__proto__: Object

And the funny thing is that some online linters fall towards browser compatibility, others towards the standard, so you can’t decide for sure if your json is browser-valid or standard-valid.

https://1drv.ms/u/s!AquVr9J7xRcsgWstdolGgysJ-p4e

[Mark SiblyKeymaster]

The Json parser definitely needs better error feedback! I’ve been using this to validate my json lately:

http://www.jsoneditoronline.org/

I think the default behaviour of the parser should definitely be ‘standard-valid’ as it ensures your json will work anywhere. but I’m open to the idea of adding some JsonParserFlags that allow things like extra trailing commas, comments in json etc.

[Author]

Posts