uber-go/zap

Dev: Colored console output

Open

#489 opened on Aug 15, 2017

View on GitHub
 (10 comments) (28 reactions) (0 assignees)Go (1,448 forks)batch import
help wanted

Repository metrics

Stars
 (22,391 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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

Contributor guide

Research direction
Look at the existing development encoder and add ANSI color codes for log levels, stack traces, and key value pairs. Ensure the production encoder is unaffected.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75