-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add comment support #15 #32
Add comment support #15 #32
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
@googlebot I signed it! |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
I will think about the better approach like #15 and left this PR until then! |
@110y how about this PR? I need comment support 😉 |
e370ad3
to
67b5c48
Compare
I would also need to add comments to the scripts but unfortunately, a regexp-based solution is not reliable enough. For example, if there is a command like this in the script:
it will become wrong:
illustration: https://play.golang.org/p/28ELu7ugA2D I think a more careful parsing is needed. I am happy to implement it but don't want to take it out from your hand either. Please, let me know if you have time for it, otherwise I will start working on it. Another note: maybe not everybody is happy with a breaking change how wrench works. Therefore, I would be more conservative and would add a command-line option to turn ON the comment removal. The default behaviour should be the original behaviour. |
WHAT
WHY