News for hackers. Stuff that matters.

A comment on YAML: probably not so great after all (2017). Parent comment

Re:YAML: probably not so great after all (2017) by artpepper2 on Wednesday June 20, 2018 @03:20PM (#17358790)
Blurg, now every tooling pipeline that uses JSON needs to include a JSMin step...
[ Parent | on HN ]
Re:YAML: probably not so great after all (2017) by Zamicol on Wednesday June 20, 2018 @03:33PM (#17358901)
If you're making comments for yourself in config files you control:

/\/\/.*/gm

https://regexr.com/3rbgb

[ Parent | on HN ]
Re:YAML: probably not so great after all (2017) by lolc on Wednesday June 20, 2018 @06:33PM (#17360457)
"hello // syntax error"
[ Parent | on HN ]
Re:YAML: probably not so great after all (2017) by Zamicol on Thursday June 21, 2018 @02:24PM (#17367925)
You are 100% correct. For not single line comments, "//" in the datastructure, and everything else there are already well tested solutions for the problem. https://github.com/sindresorhus/strip-json-comments

My point is only that this isn't a big issue. I don't understand why so many see it as a large issue. Instead, projects use non-standard YAML or other problematic solutions only because "JSON doesn't have comments".

[ Parent | on HN ]