Improve error output

[markelog]

Recent release of 1.5.0 showed, on my opinion, that we need to improve error output, either provide warning module or adapt current error module API (rename maybe) to show notifications/warnings, without line and column number.

Also this change is required for #238 issue, just like it might beneficial for plugins and rules notification.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[mikesherov]

@markelog, for something like #238 it's easy to adapt the current error output simply number truncating the error array.

However, the overall problem stems from the fact that most tools simply read the output of one of the error formats, all of which assume line and column. I'm not sure we can get away from reporting dropped rules in the normal error output without breaking the world.

Thoughts?

[markelog]

it's easy to adapt the current error output simply number truncating the error array

It's an easy way yes, but i was thinking that we need a correct message for it, if we would output say 100 errors when there could be a thousand, without any message, user would thought that we found only 100 errors in total, he would fix one, and still get a 100 errors, he would fix 10 and... you get the picture, whereas people might not look in doc for it, similar to a problem we have with nulling rules of the preset.

I'm not sure we can get away from reporting dropped rules in the normal error output without breaking the world

2.0 and break stuff, like in Limp Bizkit song

[mikesherov]

It's an easy way yes, but i was thinking that we need a correct message for it, if we would output say 100 errors when there could be a thousand,

But the default would be show all errors. Only by specifying a max would the user be seeing a possibly truncated list. But I get what you're saying.

[SgtPooki]

Are there any issues open or talks or plans for doing some sort of summarized report?

I would love to be able to just get a general consensus of how my code is looking, without actually seeing the specifics. Something like:
disallowNewlineBeforeBlockStatements: 45 errors in 5 files
disallowTrailingComma: 200 errors in 20 files
validateIndentation: 12,345 errors in 678 files

etc..

[qfox]

@SgtPooki These stats you talking about can be generated by custom reporter (afaik). Take a look at https://github.com/wurmr/jscs-teamcity-reporter

[SgtPooki]

@zxqfox Thanks but that reporter seems to output each error for each line for each file, the same as all other reporters. I did attempt to use that one before commenting here. It's output was quite ugly tbh.

Would we just need to create an additional "summary" reporter, or is there a way to pass options to reporters?

EDIT: Disregard, i'm going to write up a quick summary reporter.. it looks fairly simple.

[SgtPooki]

No time to submit it in a PR right this moment, but https://gist.github.com/SgtPooki/f13f24517b7a69b93017
http://imgur.com/FBX0C75

[qfox]

@SgtPooki That's what I mean. Well done! 🌴

[mdevils]

Wow, nice one.

[markelog]

@SgtPooki could you send us a PR?

[SgtPooki]

I sure will. I will get it done tonight.. Finally got the wheel hub pried off my car last night, so tonight is free for a todo item of my choosing. I chose you. :)

[SgtPooki]

PR = #601

[hzoo]

Any updates on this?