-
-
Notifications
You must be signed in to change notification settings - Fork 731
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
Escaping curly braces in log messages #1547
Comments
I've made a first pass over this bug and think the changes I've made at 88b2f9d represent the appropriate solution. I've added the tests that cover the two use-cases referenced above. The one thing that I think this exposes is a bug in the
@DixonDs is right in that this should probably output If this seems reasonable, I will create a PR with the changes. |
@kcamp Can you submit a PR we can review? |
@devlead Sure, will have that put together in the next day or so. |
@kcamp excellent! 👍 |
Fixed by #1863 |
It seems that is not possible to escape curly braces properly in log messages.
Information("{} {0}", 123);
leads to error "Error: Input string was not in a correct format."Information("{{}} {0}", 123);
outputs "{{}} 123". The same input tostring.Format
yields "{} 123" which is what I want to get.This is related to SharpeRAD/Cake.Powershell#25 when the powershell output contains this particular string "{}"
The text was updated successfully, but these errors were encountered: