NetDevLtd/log4js-node — pull request #2 by mab-netdev (2012-05-02 16:48:30+00:00)
Title: Fixed log4js.configure() issue setting loggers' levels to TRACE...

...even if they were previously set to something else.

log4js.configure(), log4js.configure({}), log4js.configure({foo: {...}}) (where foo != 'levels') all set every logger's levels back to TRACE even if they have been previously set to something else with setLevel.

This is seems inconsistent, given that log4js.configure({levels:{}}) preserves any previously set levels.
https://gist.github.com/2577583

This fixes that, by ensuring that setLevel(undefined || null) does not over-write a previously set level with TRACE.

Since the only time setLevel() is called within log4js.js with no parameters is when configure is called without the configuration object containing a 'levels' property, this seems like a reasonable and simple fix.