abernh 76f91427ba fix(logger.log): warn on invalid log-level ...

a warning is logged if the `log` method is used with an unknown log-level
this happens whenever people confuse the `log` method with yet another log-level-short method (like in the browser console.log)
adjusted `newLevel-test` accordingly

rel: https://github.com/log4js-node/log4js-node/issues/1042

Signed-off-by: abernh <a.bernhard@23go.de>

2021-02-23 12:02:15 +01:00

..

appenders

fix: tcp-server needs to be loaded even if no categories

2020-05-25 08:55:04 +10:00

categories.js

style: conform @param to official style

2020-05-04 09:13:36 +09:00

clustering.js

fix: handle cluster module not existing

2019-08-12 08:32:27 +10:00

configuration.js

chore: oh shit I changed the eslint rules

2019-08-01 16:57:32 +10:00

connect-logger.js

style: conform @param to official style

2020-05-04 09:13:36 +09:00

layouts.js

fix: truncation and padding for stacktraces

2019-10-22 08:58:46 +11:00

levels.js

style: conform @param to official style

2020-05-04 09:13:36 +09:00

log4js.js

fix: Adds guards for undefiend callback functions in shutdown method

2019-11-21 10:14:17 +11:00

logger.js

fix(logger.log): warn on invalid log-level

2021-02-23 12:02:15 +01:00

LoggingEvent.js

style: conform @param to official style

2020-05-04 09:13:36 +09:00