This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 28
Better Zinc Log Format #200
Comments
@SrodriguezO @sriraamas @jjudd @andyscott What do you think? |
I like the idea of adding newlines between errors. I'm also open to making the file path bold, but the biggest gains in readability seem to be the newlines. |
a |
May be it will make sense to also have `[Error] on the blank newline, so that it doesn't seem too chopped up. |
I thought underline would be a good idea too, but it makes the output look like a bunch of links |
Paths would be shorter without |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Zinc output log is getting harder to read whenever we get a lot of messages, especially with long file path and long messages.
It would be good if we can come out with an idea of improving the readability. Adding distinction to the file path would be one option, it becomes more clear where the actually message starts.
How about making it bold?
How about putting new lines?
Or we could have both?
Any suggestion will be appreciated. Thanks.
The text was updated successfully, but these errors were encountered: