Expose a property to disable color logging #299
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The TTY check assumes we are logging to stdout, however, since the logger can be changed (e.g. to a file) this check is insufficient. To work around this issue, we expose NoColor on the DefaultLogFormatter in a backwards-compatible manner. Fixes go-chi#290.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The TTY check assumes we are logging to stdout, however, since the logger can be changed (e.g. to a file) this check is insufficient.
To work around this issue, we expose NoColor on the DefaultLogFormatter in a backwards-compatible manner.
Fixes #290.
Ideally this could in the future be refactored and expose e.g.
Logger/ColorLogger, giving more control to the user and perhaps avoiding the TTY check altogether.