You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice if a few common large objects were handled specially. In particular, HTTP request and response objects, and sockets, and buffers, all tend to be astronomical. Buffers should always be truncated so that they're also not so gigantic.
There's already a JSON stringifier function there, we could just use that.
The text was updated successfully, but these errors were encountered:
Special instanceof or whatever handling or top-level objects? I'm leery of adding that because of speed and special casing for top level objects. Serializers are intended for this, but I realize that requires forethought instead of Bunyan making it easy.
Wait is that "error" a standard JS Error object (granted possibly extended with domains info)? If so, the intention is to use the 'err' serializer ... and Error instances are also special-cased if the first arg to log.info et al.
The intro provided by the current Bunyan readme sucks.
I often see stuff like this in my bunyan output:
It'd be nice if a few common large objects were handled specially. In particular, HTTP request and response objects, and sockets, and buffers, all tend to be astronomical. Buffers should always be truncated so that they're also not so gigantic.
There's already a JSON stringifier function there, we could just use that.
The text was updated successfully, but these errors were encountered: