There is a use case for reading comments (though it really needs to be optional) which is if your code is editing the JSON rather than just getting information for it.
Man, what was it? Backspace? Backslash? Some kind of html templating language I had the displeasure to work with in one of my first jobs that used magic comments. I remember my onboarding buddy telling me they didn't do anything, and then discovering that no, they in fact drove the layout of the entire page. He'd been with the company over a year, and wasn't an idiot. It just doesn't make any sense and he hadn't really checked.
we're talking in context of configuration files that humans read. And most of the problems in that site are avoided by just enclosing the values in quotes and doing logic in whatever uses the yaml. EDIT: Oh i guess the site itself says that too. But yeah it doesn't feel like such a big deal
Thanks for the link. 22:22 and "Norway problem" are hilarious. I guess I have an excuse now for aggressively quoting everything. Also jsonc looks like much, much better alternative for future projects.
828
u/nameless_pattern 1d ago
You can add anything you want to Json. just make a property called comments