Cider.config looses its comments when ]CreateProject uses it...

[mbaas2]

The .template is nicely commented, but these comments are lost when .CreateProject uses it to create the .config for a new project.

I've hit the same problem with .json files in the past and decided to add additional fields with a "_doc" suffix and treat the comments as regular strings.

[aplteam]

This requires a set of rules that restrict where such comments are allowed in order to survive. The general JSON rules are too relaxed to allow a general solution. With such restrictions (which need to be documented of course) this could be done, and no doubt that would be useful.

The alternative would be to remove the comments altogether and extend the documentation accordingly, which is certainly easier to do.