-
Notifications
You must be signed in to change notification settings - Fork 1
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
Modify the "conditional" operation or create a new operation that handles un-prefixing matched blocks #56
Comments
It has to be noted that the case where the code block contains a comment should also be handled:
I do this with the use of a double comment. |
Current design is:
We'll also change the defaults for languages that don't support preprocessors to use |
Support for multiple file formats is essential. I use:
|
The work to do the block uncommenting (blocks of line comments that is) was done here #69 and updated dotnet/templating#2 (we've moved to https://github.com/dotnet/templating). The work to set the rest of the default commenting styles is being tracked by dotnet/templating#4 in the new repo. |
Conditional handling for windows batch files using "rem" line level comments, was setup in this commit: Other commits in the same PR (still in progress) deal with nginx.conf comment processing using "#" line level comments. This is still in progress, but we'll be able to re-use it for other file types using that style of comments. |
The nginx.conf and robots.txt setup is complete with dotnet/templating@d33aa93 |
Should automatically un-comment
Content if FOO was true
whenFOO
is true and should leaveContent if FOO was false
as a literal ifFOO
as not true. The operation will need to buffer the content being written to see if the included block is uniformly commented out (needs a more rigorous definition) before committing it to the output stream.https://github.com/dotnet/cli/issues/2052#issuecomment-231299842
The text was updated successfully, but these errors were encountered: