Tom Shawver

Thanks Jeff! > People understand middleware and is a generic way to solve a lot of use cases such as excluding and only including certain fields. To be clear, exclude/onlyInclude...

I could be swayed to make syslog levels the default, but removing customizability of the levels isn't an option. That would be a dealbreaker for many current users of Bristol....

I really love this idea. I don't think an extra `if` is the end of the world, but since Bristol already has a mechanism for modifying output, I wonder if...

Hey Jared, thanks for the kind words! Logging with Cluster was brought up in Bristol's infancy, and handling it with an official feature was a consideration for awhile. But I've...

This is a great request, and I think it'll be pretty easy to address. For the 1.0 release, I've been considering adding a way to pull an array of the...

Hey Jonathan! Killer suggestion. Bristol has a stated goal of lazy-loading everything possible, so that leaves us with two options toward that goal: 1. Define a getter. Either a literal...

>Personally I'm a huge fan of config which lets me manage my configurations for multiple environments and regions easily in a hierarchical structure. That said, I can see your approach...

...now that I'm thinking about it, I suppose it would be fairly easy to support multiple targets in env vars without it getting confusing. The above 4, plus these, would...

I've been playing with this one locally. While I like what this is doing, It feels a bit offputting that the array values are logged with their numeric keys, which...

Hi @superical, thanks for this! It looks like the only thing necessary to fix the build is `npm run format`. I can run that when I'm home, but if you'd...