Global serializer invoked on child creation

描述

'use strict'

const pino = require('pino')

const logger = pino({
  useLevelLabels: true,
  messageKey: 'message',
  base: null,
  serializers: {
    [Symbol.for('pino.*')]: obj => {
      console.log('serializer')
      console.log(obj);
      return obj
    },
    
    err: (obj) => {
      console.log('err serializer')
      return obj
    }
  }
});

let l = logger.child({ app: {
  name: 'blah'
}})

serializer
{ app: { name: 'blah' } }

贡献者指南

技术栈

javascriptnodejs

领域

backend

议题类型

bug

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-3 hours

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

stale

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

Node.js basicsPino logger basics

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

40

研究方向

Investigate the pino child creation flow in the source code, specifically the 'child' method in pino.js. The issue suggests that the wildcard serializer (Symbol.for('pino.*')) is being applied during child creation rather than at log time. Look at how serializers are merged in child() and ensure they are only invoked when a logging function (e.g., info, error) is called. Check existing tests related to serializers and child loggers to understand expected behavior.