Dan Buch

@dearchap there's certainly a lot to consider! I think the help output with `|` separating mutually exclusive values works well. Do the displayed text for defaults or env vars need...

@wayan perhaps something like https://github.com/lithammer/dedent would be helpful? Then you can format your multiline strings with any amount of common leading blankspace.

@sairson Hello and sorry for the delay! Can you provide more details, such as what version of the library you are using and some example code covering your use case?

> [...] this is obviously kind of a hack, and not something simple for a library user to figure out on their own. If what I'm doing is the best...

@makeworld-the-better-one after thinking about this a bit more, I'm recalling the `Global{Type}` functions that used to be available on `*cli.Context` in v1. The example code you provide in the description...

FYI here is an extracted version of the migration source provider for consideration: https://github.com/rstudio/golang-migrate-source-aws-s3-v2

I'm attempting to make this, although I feel like I'm learning more about how pgx could be modified to allow a less gnarly integration 😂 https://github.com/DataDog/dd-trace-go/compare/v1...rstudio:contrib-jackc-pgx. If anyone else sees...

The fully wrapped version works, but is an anxiety-inducing amount of code. This attempt uses the existing pgx logger capabilities: https://github.com/DataDog/dd-trace-go/compare/v1...rstudio:contrib-jackc-pgx-logger

@felixge I'm glad you're less irked by the LoC 😂! The fully wrapped approach is (AFAICT?) going to provide deeper insights than the wrapped logger approach. You're absolutely right about...

@felixge Sorry for my delay. The timings are plausible only in that they aren't *longer* than the parent spans 😐 It's not great. I'd be up for trying a generated...