Templated Project JSON contains comments... about generator-aspnet HOT 4 CLOSED

Ok well the larger problem is that VS templates include comments as well. Should we remove those as well?

cc @rustd @madskristensen

from generator-aspnet.

Maybe tooling in VS strips comments before JSON is used? That's common solution, e.g.:
https://github.com/sindresorhus/strip-json-comments
(that is: this could be the reason why VS templates have comments in JSON sources)

from generator-aspnet.

VS will already handle JSON with comments, so I don't think that's the issue, it's more if you're roundtripping with other editors which don't (or developers on other editors).

I'm in two minds, on the one hand, it's against the spec, on the other, comments are genuinely useful and the only editor that seems to choke right now is Sublime, so a workaround could be employed for that.

My current leaning is if JSON is going to be the project format, then it should be valid JSON.

Edit: Crockford's take on this:

I removed comments from JSON because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn't.

Suppose you are using JSON to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your JSON parser.

https://plus.google.com/+DouglasCrockfordEsq/posts/RK8qyGVaGSr

from generator-aspnet.

PR #83 addresses the templates with comments in the project.json files

from generator-aspnet.