If you use parseTopicDirectives then it allows to use log levels as strings which can be lowercased or even shortened. But if you want to set top-level logging level then you have to use the parseEnum utility which is IMHO bad API, so I want to introduce another override for setLogLevel which allows to take string in any casing.
Sounds reasonable, but instead of a setLogLevel overload, it feels like it's the log level parser that should be exposed (ie proc parse(_: type LogLevel, v: openArray[char]): LogLevel or something like that) - wdyt?
If you use
parseTopicDirectives
then it allows to use log levels as strings which can be lowercased or even shortened. But if you want to set top-level logging level then you have to use theparseEnum
utility which is IMHO bad API, so I want to introduce another override forsetLogLevel
which allows to take string in any casing.