diff options
| author | Adam Bard <github@adambard.com> | 2015-10-09 17:23:10 +0800 |
|---|---|---|
| committer | Adam Bard <github@adambard.com> | 2015-10-09 17:23:10 +0800 |
| commit | 893be4215370335710ac4d77d707606abd348030 (patch) | |
| tree | 91302c7c75dbe3463ba47c3e3bcf6d2d106f368b | |
| parent | 0d0c495c701acc77047df138e169e7cc7ece5f97 (diff) | |
| parent | 7fd149485e0cbef6fc57206cb1377f261ed70278 (diff) | |
Merge pull request #1416 from AVGP/854-json-trailing-comma
Mention of trailing commas in JSON and that they should be avoided
| -rw-r--r-- | json.html.markdown | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/json.html.markdown b/json.html.markdown index 6aff2ce2..a85cecc4 100644 --- a/json.html.markdown +++ b/json.html.markdown @@ -10,8 +10,11 @@ As JSON is an extremely simple data-interchange format, this is most likely goin to be the simplest Learn X in Y Minutes ever. JSON in its purest form has no actual comments, but most parsers will accept -C-style (`//`, `/* */`) comments. For the purposes of this, however, everything is -going to be 100% valid JSON. Luckily, it kind of speaks for itself. +C-style (`//`, `/* */`) comments. Some parsers also tolerate a trailing comma +(i.e. a comma after the last element of an array or the after the last property of an object), +but they should be avoided for better compatibility. + +For the purposes of this, however, everything is going to be 100% valid JSON. Luckily, it kind of speaks for itself. ```json { |