diff options
| author | iirelu <totallymyrealemail@hush.ai> | 2014-03-01 19:46:36 +0000 |
|---|---|---|
| committer | iirelu <totallymyrealemail@hush.ai> | 2014-03-01 19:46:36 +0000 |
| commit | 9894e0ce15a618910f9335e2e46b18ff805d9438 (patch) | |
| tree | aafc560dfab3dd63e80230d8cfd9d6ccdaf87f0f /json.html.markdown | |
| parent | e5bec988bb56307975913232841d5e604534f4e1 (diff) | |
slightly expanded on json.html.markdown
Removed useless stuff, added new stuff.
Diffstat (limited to 'json.html.markdown')
| -rw-r--r-- | json.html.markdown | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/json.html.markdown b/json.html.markdown index 7df47a4a..f86f0ae9 100644 --- a/json.html.markdown +++ b/json.html.markdown @@ -5,18 +5,17 @@ contributors: - ["Anna Harren", "https://github.com/iirelu"] --- - 0 As JSON is an extremely simple data-interchange format, this is most likely going 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, everything is going to -be 100% valid JSON. Luckily, it kind of speaks for itself. +C-style (//, /\* \*/) comments. For the purposes of this, however, everything is +going to be 100% valid JSON. Luckily, it kind of speaks for itself. ```json { "numbers": 0, - "strings": "Hellø, wørld. All unicode is allowed.", + "strings": "Hellø, wørld. All unicode is allowed, along with \"escaping\".", "has bools?": true, "nothingness": null, @@ -25,7 +24,7 @@ be 100% valid JSON. Luckily, it kind of speaks for itself. "objects": { "comment": "Most of your structure will come from objects.", - "array": [0, 1, 2, 3, "banana", 5], + "array": [0, 1, 2, 3, "Arrays can have anything in them.", 5], "another object": { "comment": "These things can be nested, very useful." |