I just discovered jsonc.org, thank you for your efforts!
JWCC stands for "JSON With Commas and Comments," a standard proposed by Nigel Tao that adds line comments, block comments, and trailing commas to the JSON format. His blog post1 is worth reading for anyone interested in jsonc.
Contrary to the blog post, I personally prefer the name "JSONC". It's clearly more concise, easier to understand, and easier to promote, and it represents "JSON With Commas and Comments" in almost every existing context.
For the same reason, I believe the jsonc standard should enforce support for trailing commas. VSCode's default settings shouldn't hinder this widespread convention. I think "allowTrailingComma" of ".jsonc" files should be true by default. If some kinds of ".jsonc" configurations support comments but not trailing commas, "allowTrailingComma" should be explicitly set to false.
I just discovered jsonc.org, thank you for your efforts!
JWCC stands for "JSON With Commas and Comments," a standard proposed by Nigel Tao that adds line comments, block comments, and trailing commas to the JSON format. His blog post1 is worth reading for anyone interested in jsonc.
Contrary to the blog post, I personally prefer the name "JSONC". It's clearly more concise, easier to understand, and easier to promote, and it represents "JSON With Commas and Comments" in almost every existing context.
For the same reason, I believe the jsonc standard should enforce support for trailing commas. VSCode's default settings shouldn't hinder this widespread convention. I think "allowTrailingComma" of ".jsonc" files should be true by default. If some kinds of ".jsonc" configurations support comments but not trailing commas, "allowTrailingComma" should be explicitly set to false.
Footnotes
https://nigeltao.github.io/blog/2021/json-with-commas-comments.html ↩