Changes from @japgolly's branch
See original GitHub issueAs first mentioned in https://github.com/Duhemm/sbt-errors-summary/issues/8, on my branch I made the following changes:
- changed colours of filenames
- made most colours bold so they are more readable on black backgrounds (at least in my envs)
- in the by-filename report at the end
- sort by filename
- only print if more than one file
- print total error/warning count per file
- don’t print line numbers
- consolidate problem ids where possible (eg.
[1-4,9]
instead of[1,2,3,4,9]
)
- print total errors and warnings
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Refs - japgolly/scalajs-react · GitHub
The names evolved incrementally and are now a bit misleading. The types are named "typed" and "untyped". What are the differences? "Typed" refs...
Read more >shapeless 2.2.0 released! - Miles Sabin
js by branching and merging (as opposed to managing platform variations within a single branch) is working out very smoothly. It means that ......
Read more >japgolly/scalajs-react - Gitter
Hi all, anyone else seen the Multiple (2) (unconditional) routes specified error. I see it for two routes after upgrading but can't find...
Read more >Commit Graph Mono Color - sunter/svg-android - Agit
... c19b0bd Merge remote-tracking branch 'remotes/japgolly/master' by Silin Nick ... 3334783 Changed Maven groupId by David Barri 2013-01-31 08:11:36 +1100 ...
Read more >Git is too hard - Hacker News
But I will switch between multiple feature branches as necessary. And to keep up with master, I'll rebase my feature branch onto origin/master ......
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
Hi, I’ve made some changes just now to put back the line numbers in the summary lines at the bottom. I’ve also put the total number of errors per file on the right. It’s nice and easy to read but still not intuitive if one doesn’t know what the numbers mean…
Anyway, here’s how it looks now. WDYT?
My confusion is I thought one number was identifying the error and the other the number of occurrences in the file, rather than the line number.
Anyways, cross-linking that conversation here: https://github.com/Duhemm/sbt-errors-summary/issues/12.