underlyingLogger got a lot more complex about kotlin-logging

[github-actions]

Thank you for reporting an issue. See the wiki for documentation and slack for questions.

[oshai]

We can definitely move that complexity to the lib itself. But for your case, why not just use the following:

Configurator.setLevel(logger.name, Level.DEBUG)

As the name just passed as is between the loggers in different layers, I don't see a reason not to use the name of the logger itself.
Any other solution in the lib itself will still require a cast, as with MPP, not all platforms has the concept of underlyingLogger which is why this interface exists.

[2x2xplz]

Thanks for the quick reply, yes this indeed appears to work. Perhaps this could be added to the docs? That code that required underlyingLogger in v3 may not need it anymore in v5? Honestly I would never have thought to simply remove the underlyingLogger, if it was necessary in v3 I just assumed it was necessary in v5, and the code block above from the wiki seems to support that by continuing to require underlyingLogger.

[oshai]

I suspect that in V3 underlyingLogger is also not required in this case.

[oshai]

Is there still an issue here?