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
nestedKey (see #759) seems useful enough in concept to warrant a specialized implementation to support it for log attributes added as part of child-logger creation.
Perhaps it could use a special string-building implementation that concatenates the stringified chindings into [nestedKey] during childLogger.<logLevel>({attrs}, ...) (something like {[nestedKey]: {...chindings, ...attrs}} would do if they were objects).
(Alternatively, it could be worth considering placing existing metadata into {meta: {...}}, such that Pino owns the object in meta:, and loggers & child-loggers can own the remainder of top-level namespace)
nestedKey (see #759) seems useful enough in concept to warrant a specialized implementation to support it for log attributes added as part of child-logger creation.
Perhaps it could use a special string-building implementation that concatenates the stringified chindings into [nestedKey] during
childLogger.<logLevel>({attrs}, ...)
(something like{[nestedKey]: {...chindings, ...attrs}}
would do if they were objects).(Alternatively, it could be worth considering placing existing metadata into {meta: {...}}, such that Pino owns the object in meta:, and loggers & child-loggers can own the remainder of top-level namespace)
@matthewadams thoughts? (also: thanks!)
The text was updated successfully, but these errors were encountered: