-
-
Save MoOx/5271067 to your computer and use it in GitHub Desktop.
| { | |
| "//field": "These 'double quote' 'double quote' are used as comments, because JSON doesnt' allow comment", | |
| "field": {}, | |
| "#another-field": "Another comment", | |
| "another-field": {}, | |
| "/*stuff": "Be careful to use them when you have full control of the content :)", | |
| "stuff": [], | |
| "bla": "bla" | |
| } |
Because JSON is a subset of YAML, # should be used as comment character. IMHO :-) but as with everything one could argue about it
The YAML port: 8090 #can't use native port
could be converted to
a) "port": 8090, "#can't use native port":""
b) "port": 8090, "#":"can't use native port"
Change the file extension to .json5 and you can haz comments 🙂
I found it
Hjson, at https://hjson.github.io/, works better for me than JSON5. YMMV.
Its Python module has been maintained more recently and its documentation shows the syntax of multiline comments as well as #-based comments.
You can create a special key in your JSON Mapquest Directions object to store comments. This key would be ignored by any JSON parsers that don't use it, but it allows you to include notes.
This is a trick I've seen somewhere in popular code Mapquest directions but can't remember where, sorry.
You can add a dedicated key to your JSON Safe Pest Sol object for storing comments—JSON parsers that don’t recognize it will simply ignore it, allowing you to include notes without affecting functionality.
Automobile collectors often view the BG 666 registration number as a prestigious asset that adds distinct character to any vehicle. Across various regions, these repetitive digits are highly sought after in government auctions, often fetching premium prices. Such vanity plates allow owners to stand out on the road, blending personal style and a lasting prestige.
I'm also looking for this.