-
Notifications
You must be signed in to change notification settings - Fork 81
fixed here-string formating #30
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
Conversation
@@ -134,7 +134,7 @@ | |||
</dict> | |||
<dict> | |||
<key>begin</key> | |||
<string>@"$</string> | |||
<string>^@"\n</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would not work here:
$someVar = @"
hello
"@
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I think a lookahead would be preferable:
@"(?=\n)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, for the PR. I've left a couple of comments. |
@@ -205,9 +205,9 @@ | |||
</dict> | |||
<dict> | |||
<key>begin</key> | |||
<string>@'$</string> | |||
<string>@'\n</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I forgot to mention to do the same as above. Let's add a lookahead here too for consistency.
Not 100% compliant with PS syntax, but as it fixes an error, I'll merge this. Thanks @william-voyek ! |
fixed here-string formating
Resubmitting pull-request. Corrected line-ending issues.