rules_scala icon indicating copy to clipboard operation
rules_scala copied to clipboard

Better Zinc Log Format

Open borkaehw opened this issue 5 years ago • 6 comments

The Zinc output log is getting harder to read whenever we get a lot of messages, especially with long file path and long messages. Screenshot from 2019-07-23 16-15-32

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? Screenshot from 2019-07-23 16-14-20

How about putting new lines? Screenshot from 2019-07-23 16-16-58

Or we could have both? Screenshot from 2019-07-23 16-17-44

Any suggestion will be appreciated. Thanks.

borkaehw avatar Jul 23 '19 22:07 borkaehw

@SrodriguezO @sriraamas @jjudd @andyscott What do you think?

borkaehw avatar Jul 23 '19 22:07 borkaehw

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.

SrodriguezO avatar Jul 23 '19 22:07 SrodriguezO

a colon(:) after the line number can also make things a little better. Am not sure about underline, but I think the newline, does run the risk of not-so-compact output, while improving readability.

sriraamas avatar Jul 23 '19 23:07 sriraamas

May be it will make sense to also have `[Error] on the blank newline, so that it doesn't seem too chopped up.

sriraamas avatar Jul 23 '19 23:07 sriraamas

I thought underline would be a good idea too, but it makes the output look like a bunch of links

SrodriguezO avatar Jul 23 '19 23:07 SrodriguezO

Paths would be shorter without src/main/scala pasted everywhere :/

pauldraper avatar Oct 14 '19 18:10 pauldraper