-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow comments in options file? #2945
Comments
what about using tsconfig.json instead? |
I haven't heard of that - will do some research. |
Yes. It doesn't solve the problem, but it is nice to know. 👍 |
JSON specification does not allow having comments (Note: Newtonsoft JSON.NET provides non-standard aux feature to allow comments). It was removed at some point from specification as an "improvement", to which many people objected. Nonetheless, it would be really handy to have @madskristensen has also managed to validate and provide intellisense for .jshintrc, .jscsrc etc. in VS2013 and VS2015 via editor extensions, which signifies that it is a very viable option! (only Windows team needs to allow creating a |
tsconfig now supports comments, see #4987 |
E.g. when running
tsc @TSCOptions.txt
, it would be cool if there was a way to include comments in the options file since they can become very long. For instance:Comments in this example are preceded with a
#
and can be inline or on their own line. Antything after a#
would be stripped prior to compilation.The text was updated successfully, but these errors were encountered: