I'm replacing my current use of console.log with whistlepunk, finally... and i'm about to start putting it into my rabbus library.
i would like to use whistlepunk in rabbus without specifying a configuration for output / level / etc?
in other words, i want to be able to call logger.debug and logger.warn, etc., but i don't want to pre-configure the output location of the logging from within rabbus. i want to let the primary application instance determine where the logs should go, and what level of logs to show.
is this possible with whistlepunk, at the moment? I was looking at wascally, and i see it is configuring a level and adapter... is that really the best idea? shouldn't wascally (and other libraries) let the application process determine the adapters and level to log?
I'm replacing my current use of console.log with whistlepunk, finally... and i'm about to start putting it into my rabbus library.
i would like to use whistlepunk in rabbus without specifying a configuration for output / level / etc?
in other words, i want to be able to call
logger.debugandlogger.warn, etc., but i don't want to pre-configure the output location of the logging from within rabbus. i want to let the primary application instance determine where the logs should go, and what level of logs to show.is this possible with whistlepunk, at the moment? I was looking at wascally, and i see it is configuring a level and adapter... is that really the best idea? shouldn't wascally (and other libraries) let the application process determine the adapters and level to log?