"Unfortunately JSON doesn't support comments."
What were they thinking? Even XML supports comments.
Is it legal to repeat the same name for a (string) value at the same
level? For example:
{
"Comment" : "A comment",
...
"Comment" : "Another comment",
...
"Comment" : "A third comment",
...
}
If not, one would have to invent lots of names -- one per comment. This
would would make updates to the JSON awkward, and the obvious scheme of
"Comment1", "Comment21", ... "Comment148" etc. would imply a spurious
order. (And using UNIX timestamps like in "Comment_1569010686", even if
unique, would be really ugly and confusing.)
Of course one might use an approach like:
{
"A comment": null,
...
"Another comment": null,
...
"A third comment": null,
}
assuming no two comments are the same (which is not always true).
On Fri, 20 Sep 2019 14:50:16 -0400
Mike Kaply <[email protected]> wrote:
> Unfortunately JSON doesn't support comments.
>
> You can at invalid entries if you want and it will still parse fine.
>
> "Homepage_Comment": "some text"
>
> Mike
>
> On Fri, Sep 20, 2019, 2:41 PM Eddie Rowe
> <[email protected]> wrote:
>
> > If I put the same type of comment line in the policies.json that I
> > have in the in the autoconfig.js, Firefox does not process the
> > file. Is there no option for putting comments in this file?
> >
> >
> >
> > // This line is a comment line.
> > https://support.mozilla.org/en-US/kb/customizing-firefox-using-policiesjson
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
[email protected] with a subject of "unsubscribe"
