Open recursion-ninja opened 5 years ago
You could just ignore parse errors if you don't care about them. However, in many cases you can change the flags to HLint to make them parse, so I by default report then.
I think reporting the parse errors is useful and informative, but they shouldn't be included in the hint total.
I think the last line should read:
3 hints, 2 parse errors
This way you don't need to mentally parse the output to determine if there were parse errors when HLint ran, HLint tells you there were parse errors.
That seems quite reasonable to adjust the status line. PR welcome!
When I run
hlint
on our code base there are 3 parse errors and two hints, however the textual report says "5 hints".Parse errors aren't really "hints," so they shouldn't counted in the total.