General feedback

[stamminator]

Thanks for hosting this. An "unofficially official" place outside of VSCode's repo to discuss JSONC is needed.

JSONC doesn’t allow trailing commas; however, we encourage parsers to be lenient and handle trailing commas gracefully where possible to reduce the risk of human edits introducing parsing errors.

I initially wanted to complain about this, but after looking at VS Code's JSONC docs, I realize you're correct. Trailing commas just make sense for both minimizing human-caused parsing format errors and for more accurate git blames, but until VS Code mans up, officially supports it, and formalizes the spec, there's nothing to be done.

Would you consider enabling the Discussions section for the repo? This issue, for example, seems more fitting for that rather than an Issue.

[DecimalTurn]

Would you consider enabling the Discussions section for the repo?

Thanks for the suggestion regarding discussions, it's indeed a good idea to have them enabled on such repo. So, there we go!

Thanks for hosting this.

The funny this is that I'm using GitHub Pages for hosting, so technically Microsoft is indirectly hosting it since they own GitHub 😅.

[ell1e]

Since I think trailing commas are important to not repeat the mistake of JSON to make it annoying to write, and since VS Code already enables them in most user-facing places anyway, I requested they rethink this for their parser along with a pull request. Feel free to weigh in.

(I don't think VS Code formalizing the format is needed, this is happening in various other places like the spec I'm involved in, or here.)