I've never had a need for comments that `{ "comment": "Hello, world" }` couldn't solve. Dangling commas would be nice, but between my auto-formatting editor and `JSON.stringify()`, they're never an issue either.
It certainly is more for the usecases where you don't use JSON in the intended way (communication between two machines) but as a config, explaining possible values or at least give a URL for a documentation of the config file format.
Interesting; I haven't come across this before. I wonder why they don't just ignore unrecognised keys. Or, at least, give a warning, but continue to work otherwise.
I've never had a need for comments that `{ "comment": "Hello, world" }` couldn't solve. Dangling commas would be nice, but between my auto-formatting editor and `JSON.stringify()`, they're never an issue either.
It certainly is more for the usecases where you don't use JSON in the intended way (communication between two machines) but as a config, explaining possible values or at least give a URL for a documentation of the config file format.
Doesn't work with strict schema validators that disallow unknown keys. I'm looking at you, tauri.conf.json.
Interesting; I haven't come across this before. I wonder why they don't just ignore unrecognised keys. Or, at least, give a warning, but continue to work otherwise.