Logger level doesn't update transports level

[emmanueldiaz]

I have a scenario where I need multiple loggers in a winston instance.
So let's say you have this code:

const winston = require('winston');

winston.loggers.add('category1', {
  console: {
    colorize: true,
    level: 'info',
    label: 'category one'
  },
  file: {
    filename: '/path/to/some/file'
  }
})

const category1 = winston.loggers.get('category1');

const testLogger = () => {
  category1.debug('debug test');
  category1.info('info test');
  category1.warn('warn test');
  category1.error('error test');
}

At this point category1.level is info because it is the default level assigned to the logger.
So, if we run testLogger() we won't see the debug message.

Let's say that we want to change the logging level to error. If we do category1.level = 'error' now category1.level will be error, but testLogger() will still show info, warn and error messages.

In order to get category1 to only show error we would need to assign category1.transports[0].level = error.

Shouldn't just changing the logger level directly affect the logging level of the attached transports?
If this the expected behavior, then what is the purpose of having a level for the logger itself?

[indexzero]

This is a fair point. Under the covers we are using the pipe event to get the initial value from the parent logger in the transports, but the API exposes no way to update all of those transports if you wish.