prefix warnings and errors with their severity #6
Conversation
This file contains hidden or 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
for logs and terminals that don't support color
BearAlliance
force-pushed
the
grouped-severity-prefix
branch
from
b4d874a to
16f0e0f
Compare
Owner
|
Thanks for your contribution! The change makes sense to me. |
Owner
|
📦 Published as v2.4.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For logs and terminals that don't support color
First of all, great formatter!
My server logs don't save color output. On large projects, it's very difficult to find the one error in between 600 warnings.
This change just prefixes warnings and errors with their severity, so they can be searched for
ex.
Existing (no color) Is this an error or a warning?
Existing (color)
Proposed (color)
