Open temsa opened 7 years ago
@lrlna ? ☝️ :)
Hey @temsa! Thanks for using this lil package! I think at this point I don't want to add this as a feature, mainly because pino-colada is meant to a be a very simple to use and allowing for options is gonna open a can of warms I don't want open.
If I need to output out objects when debugging, I usually just go with log.debug()
for smaller stuff and the plain ol console.log/error/
for when I need bigger output. It's not pretty, but at that point I am stuck, so it's the best way to get unstuck for me rather than a more verbose option.
so i just ran into this as well! frequently, when emitting an error i'll add a bunch of values to the log line to provide context for the error, but this is swallowing all those extra options.
this is a problem with local dev since those things are there specifically to help debug issues; using console.log and pino seems like overkill?
Would love to use pino-colada
, but going to have to give it a miss given the inability to include a bit more in the output.
Hey !
First thanks for pino-colada, it's really great !
However, I have a small usage issue with it, because while pino-colada removing most of the verbose stuff especially regarding requests is awesome, it would be great to have at least small objects with few properties outputed, at least in a
verbose
like mode (maybe with a threshold on the number of non object subprops )@lrlna Are you open to such a feature ? Would you want to implement it, or would you prefer a PR ?