I am not so sure we should add that. The JSON spec explicitly does not allow comments because of fear of abuse (that the comments would be used to add semantic meaning outside the spec).
I have to think about that. In any case, I think comments with open/close are generally more useful. > On 08 Jun 2015, at 16:12, Guillermo Polito <[email protected]> wrote: > > Hi Sven, list, > > I'm using Pillar, and thus STON for its configuration file. And since I want > users to change configuration files as they want, I wanted to add some > comments explaining the meaning of the file fields. > > This raises the question: How can I write comments in a ston file? I was > checking the STON reader and it looks like that is not supported. > > What should be a good comment format? > > { > /* The site id is.... */ > % comment line > ## comment line > -- comment line > "siteid" : "" > } > > Guille
