Due to pino handle customLevels as object often people will try to use like that in pino-pretty, so receiving a object instead of a string when using in code level as a transporter in pino would improve the understanding and use of the lib.
To work like that, instead of transforming the object to string and keeping two instances who had the same value but in different types:
Due to
pino
handle customLevels as object often people will try to use like that inpino-pretty
, so receiving a object instead of a string when using in code level as a transporter inpino
would improve the understanding and use of the lib.To work like that, instead of transforming the object to string and keeping two instances who had the same value but in different types: