[question] Why are semicolons reported as errors?

[joshyrobot]

I was recently writing an AVA test to check my formatting, and I noticed that extra semicolons are considered errors instead of warnings. Semicolons aren't needed, but they wont break your code either, so shouldn't it be a warning?

[Flet]

This is a bit of a loaded question! :)

Some rules in standard are for catching commit errors and others are stylistic choices that help make code clear and consistent. All rules in standard are reported as errors for simplicity.

Regarding semicolons, there is some great material and references here: http://standardjs.com/rules.html#semicolons

From standardjs.com:

At the end of the day you have to 'just pick something', and that's the whole philosophy of standard -- its a bunch of sensible 'just pick something' opinions.

• For folks who prefer semicolons, semistandard is a good choice.
• Some folks will even use eslint-config-standard directly with eslint and override/change rules as they see fit.

I hope this information helps!

[joshyrobot]

Ok, so I should just ignore the warningCount because it will always be reported as an error? And also, I have no problem with removing semicolons! :)

[feross]

You can safely ignore warningCount. It will always be zero when using standard or eslint-config-standard.