Open v1nc3n4 opened 9 years ago
It is not treated as an empty string, but as null
Yes indeed.
I don't know if we can do much about this, given XML is string only it will always be normalized after..
What about changing the key for the NullHandler
or renaming it? for instance:
<monolog:config>
<monolog:handler name="nolog_handler" type="nolog" />
</monolog:config>
I'd rather not change it but maybe we can have an alias as workaround for xml.
what about BlackHole
? faced same issue today.
I would go with null_handler
to keep the same semantics.
Do someone want to submit a PR?
null_handler
is fine with me, but the fact that the handler never bubbles makes it in fact behave more similar to what I'd expect from a "black hole" (see #399 for more about this issue)
Hi,
I'm working on a Symfony 2 application, and I'd like to temporary disable logging. I found that adding the
NullHandler
on top of the configured handlers shall do the job. Here's my monolog XML configuration:However, when I access a web page, this error occured:
It seems the
null
type in the XML parameter is treated as a blank string, and I guess there may be an issue in theConfiguration
class of the bundle. What is your opinion?Thanks for your help, BR