Feedback: json vs jsonc

[davidsneighbour]

I don't know what JSON parsers this project uses for the configuration file, but sometimes I wish I could add some form of a comment to some of my settings. Having JSONC as a format would enable us to just add some inline comments. I know it looks like a proprietary format, but adding faux elements to my JSON to comment on things feels bloated and false :D

Other formats like YAML and TOML have commenting features.

[michaeltlombardi]

I would love to be able to use JSONC or YAML as the configuration document language. Much more maintainable for me and I use comments extensively.

[estruyf]

Front Matter uses the parser you mentioned.

You can also add your file association that VSCode should treat your JSON file as JSONC.

"files.associations": {
  "frontmatter.json": "jsonc"
}

I will check if this file association can be added by the extension itself.

[estruyf]

Added the file association in the default configuration of the extension. That way, you don't have to do anything.

[michaeltlombardi]

Immediately going to update my repos to use this. It looks like this is scoped to make frontmatter.jsonc "just work" - would be great to get this for the other config files if possible (and happy to add an issue for that if it's considered a different scope).

[estruyf]

In the beta and upcoming version, you can just keep using the frontmatter.json file, no use to update it to jsonc. VSCode will use it as jsonc as I defined to treat frontmatter.json like that.

[michaeltlombardi]

Ohhh! I misunderstood. That's rad. Similar question though about comments/format in the other files (like in the .frontmatter folder).

[estruyf]

I can add it for any json file in the .frontmatter/config folder as well, makes sense!