Akshay Shah

Hi @mavogel - I'm not at Uber anymore, so I'm not actively working on zap. Try @abhinav or @prashantv.

What would the signature of `zap.Stringers` be? If I have a type `*Foo` that implements `io.Stringer`, you can't pass `[]*Foo` as `[]io.Stringer` - you have to allocate a new slice...

This is documented indirectly [on the `EncoderConfig` struct](https://godoc.org/go.uber.org/zap/zapcore#EncoderConfig), where `EncodeName` is documented as the only optional encoder. I'll happily merge a PR that improves the documentation for this.

I'm up for this, but only if we can also do bulletproof TTY detection. I'd much rather have uncolored logs than see escape codes in non-interactive environments.

I'm happy to look at PRs for this, but really don't want to depend on any pre-1.0 or unversioned libraries.

OP's intention was that the default interactive development experience looks less like a wall of undifferentiated text; one of the options was to enable colors by default. Honestly, we still...

I'm not sure how to debug without a great deal more information; internally, we install this exact package, via the same dep+Cloudflare mechanism, thousands of times a day. * Can...

Copied from #387 ## Un-export Field internals The original plan (see #13) with fields was to keep the implementation details completely private, and the only way to use a field...

## Unify the `zap` and `zapcore` packages The intention here was to separate user-facing APIs from APIs relevant only to extension authors. Unfortunately, the division has only made things more...

# Configurable field order in the console encoder Not everyone likes the order in the current console encoder. Making this configurable would be nice.