Closed japgolly closed 7 years ago
I was thinking it might be an idea to make all the colours configurable but on the other hand, it's just as easy to fork and local publish for oneself. I made mine look like this:
Thanks for the report! I just tried your branch. The result of your whole set of changes look really good, and make everything even easier to read.
Would you mind opening a PR with your config?
Yeah I was going to ask you about that. I made a bunch more changes, are you happy with all of them? I can create a PR with all the changes or just a subset that you're happy with.
To summarise my changes:
[1-4,9]
instead of [1,2,3,4,9]
)All of them sound good to me! Looking forward to the PR!
Great, I'll get a PR ready later this week!
Hey @japgolly, I've been looking in more details at your changes, and I had missed that you removed the line numbers from the summary. That's basically the reason why I created this reporter :( Can you think of a way of adapting your changes while keeping the line numbers from the summary? Maybe a flag that would let users switch between the 2 modes?
@japgolly Colors and such are now completely configurable. You can set, for instance:
reporterConfig := reporterConfig.value.withErrorIdColor(BLUE + BOLD)
.withSourcePathColor(YELLOW + UNDERLINED)
With the default colour schemes for xTerm, Linux console, Rxvt, the dark blue on black background is near unreadable. Bold blue would be much better. Red is similar but not as bad: