Gracefully initialize/auto-detect behind the scenes? about yansi HOT 3 CLOSED

I don't think we should make any decisions for the user here. They should be able to (or be able not to) conform to any standard or non-standard they want. But I don't quite understand your example. Can you be specific, perhaps with code?

from yansi.

Let's break apart the users involved

• User running a program
• Program author
• Test crate author

Ultimately, the color policy is left for the program author to decide but generally will follow a standard the user running the program expects.

Now, a crate author might try to make testing easier, and want colored output to help, like pretty_assertions. The program author would then be using this as part of their testing. The user running the program never sees this.

Options for test tool crates, like pretty_assertions

• Hard code colors on
• Put colors behind a feature flag
• Use a once_cell to call color detection code and store the value

Rather than every test crate handling this on their own, what if we provided a feature flag that had logic from #18 in it and would ensure we do the "right thing" in these cases.

from yansi.

I don't think conforming to a variety of standards should be yansi's prerogative. I don't want yansi to be opinionated here: I want it to fit every use-case. If another crate wants to provide utilities that conform to these standards, then that's totally great. But I think we should leave it to other crates.

from yansi.