uber-go/zap

Dev: Colored console output

Open

#489 创建于 2017年8月15日

在 GitHub 查看
 (10 评论) (28 反应) (0 负责人)Go (22,391 star) (1,448 fork)batch import
help wanted

描述

We should color the output under the development config for better readability in a console.

Some ideas,

  • Color log lines based on levels
  • Use a muted color for stack traces belonging to vendored dependencies and something brighter for the main application
  • Color keys and values for key-value pairs differently

贡献者指南

技术栈
go
领域
backenddeveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic GoFamiliarity with zap's configuration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Investigate the existing console encoder in zapcore to understand how output is formatted. Look into adding color based on log levels (e.g., red for errors, yellow for warnings) and consider using different colors for stack traces from vendored dependencies vs. application code. The issue mentions key value pair coloring; explore using ANSI escape codes. Check comments for any prior discussion or partial implementations.