Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
[cookbook][logging]Bug in xml monolog format example#2488
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Changed \n => 
 in xml example.
burci commentedApr 11, 2013
Hm, well i dont know if this will be good at the site, or should i write as 
 in the code? |
wouterj commentedApr 11, 2013
I actually can't see the problem? When I view it in the browser, everything is correct. The Sphinx parser will already take care of escaping characters |
burci commentedApr 11, 2013
When i write it down here in markdown it did not escaped well, but then everything is fine with this patch. |
stof commentedApr 11, 2013
@burci The doc is not written in Markdown |
burci commentedApr 11, 2013
@stof I mean when I opened the ticket here at github, I had to change the description because of 
 not escaped well. That makes me think that maybe the same can happen with reST, but since then i checked and it is correct in this way. |
stof commentedApr 11, 2013
@burci you had to change the description because you are not using a Markdown code-block... |
burci commentedApr 11, 2013
@stof true |
[cookbook][logging]Bug in xml monolog format example
weaverryan commentedMay 3, 2013
Hey Peter! Wow, very subtle fix, but you're absolutely right: the new change you make breaks perfectly in XML. Thanks! |
Changed \n => 
 in xml example.