Bring clarity when colour aren't available
See original GitHub issueI’m concerned by the UX when colour aren’t available. What does this mean?
[error] /src/main/scala/Bar.scala: 2 [1], 4 [2]
[error] /src/main/scala/Foo.scala: 2 [3]
Brainstorming, I wonder if it would be more intuitive if it were:
[error] /src/main/scala/Bar.scala: [1] (2 times), [2] (4 times)
[error] /src/main/scala/Foo.scala: [3] (2 times)
Another alternative, perhaps, is to use letters rather than numbers to label the errors. So it might be [A] (2 times)
I was also playing around… what about [1] (2x)
as short hand for “2 times”…
I don’t have any clear winners, but I thought I should open an issue to start a conversation.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Zedd - Clarity ft. Foxes (Official Music Video) - YouTube
True Colors is available now: http://smarturl.it/ZeddTrueColors Get tickets to Zedd's True Colors Tour at http://Zedd.net.
Read more >The Influence of Colour on Memory Performance: A Review
Colour images were reported to have better memory recognition over black-and-white, but the differences were small. However, there were no significant ...
Read more >Diamond Color vs Clarity: Which Is More Important?
Bottom Line Recommendation: When buying a diamond, it's important to consider both color and clarity. Both have an impact on a diamond's appearance,...
Read more >Color Psychology in Marketing and Branding is All About ...
Color psychology in marketing and branding is more complex than “green conveys calm.” Consider these studies to make better decisions.
Read more >The Psychology of Color: How Do Colors Influence Learning?
Green is a good color for keeping long-term concentration and clarity, making it a good choice for an office – as opposed to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
One reasonably common way to identify line numbers is with an ‘L’ prefix. We can extend that by prefixing errors with ‘E’.
A ‘legend’ at the start (or end) of the error report would be nice though:
Another alternative to letters is prepending with a hash, so it kind of looks like an issue number:
#1
.