6 ms·
There _is_ a json variant with comments, so that’s what you’ve seen. Not all parsers support that though
by hutattedonmyarm 1mo ago
There _is_ a json variant with comments, so that’s what you’ve seen. Not all parsers support that though
- jeroenhd 1mo agoIt's non-standard JSON, so you can probably just assume most patsers don't support any given commented parser. At least XML permitted comments, fhe shift to JSON on everything almost makes me nostalgic.
- DenisM 1mo agoWhen you get too nostalgic just think back to XSD type system in Xquery. That should cure the nostalgia real fast.
- xgulfie 1mo agoAre you denying what I've seen with my own eyes? I am saying it was an object like this: { "//":"make sure these are divisible by 8", "width": 640, "height": 480 }
- wincy 1mo agoNot the person you’re replying to but you were clear in what you were describing. It seems like they were thinking of some json parsers that’ll ignore just straight up anything after // before a new line in JSON (looking at you visual studio). So a .NET dev who has never touched anything but Visual Studio may make comments in the appsettings.json for a .NET project and it made all my command line parsers throw errors. Thanks Microsoft.
- hutattedonmyarm 1mo agoOooh, I misunderstood. I thought you were seeing this: https://jsonc.org/ https://jsonc.org/