summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorMarco Scannadinari <m@scannadinari.co.uk>2014-06-08 22:00:14 +0100
committerMarco Scannadinari <m@scannadinari.co.uk>2014-06-08 22:00:14 +0100
commit8348e27660026f70f57ca95dbd4b175adada0410 (patch)
treea7b176132ceb85416030d634f2d94319c2cf1fae
parent20f5a00de42d32a14083f039a0ea7c2be9255e14 (diff)
Add extra detail
-rw-r--r--json.html.markdown9
1 files changed, 9 insertions, 0 deletions
diff --git a/json.html.markdown b/json.html.markdown
index f86f0ae9..28906116 100644
--- a/json.html.markdown
+++ b/json.html.markdown
@@ -3,6 +3,7 @@ language: json
filename: learnjson.json
contributors:
- ["Anna Harren", "https://github.com/iirelu"]
+ - ["Marco Scannadinari", "https://github.com/marcoms"]
---
As JSON is an extremely simple data-interchange format, this is most likely going
@@ -14,6 +15,9 @@ going to be 100% valid JSON. Luckily, it kind of speaks for itself.
```json
{
+ "key": "value",
+
+ "keys": "must always be enclosed in quotes (' or \")"
"numbers": 0,
"strings": "Hellø, wørld. All unicode is allowed, along with \"escaping\".",
"has bools?": true,
@@ -42,6 +46,11 @@ going to be 100% valid JSON. Luckily, it kind of speaks for itself.
[0, 0, 0, 1]
]
],
+
+ "alternative style": {
+ "comment": "check this out!"
+ , "comma position": "doesn't matter - as long as its before the value, then its valid"
+ , "see for rationale": "https://gist.github.com/isaacs/357981"
"that was short": "And, you're done. You know know everything JSON has to offer."
}