Warning for style

[denis-sokolov]

Is there a design decision on why the warnings feature of eslint is not used? One could consider marking only the real error-catching rules as errors, and the rest of styling distinctions as warnings.

This allows the users to prioritize efforts on fixing errors first, and the style second. More importantly, the currently proposed best practice of running standard as part of npm test results in quick test cycle (i.e. TDD) users being highly annoyed, as it is impossible to iterate quickly if every tiny styling issue breaks the tests. Warnings would not affect the return code, resulting in a better experience.

[denis-sokolov]

Disregard that, did not find standard/standard#108 before, sorry.

[feross]

No problem. Thanks for opening a thoughtful issue. :)

[marcinn]

I read the docs and this discussion. Just want to say that "All rules should be errors" is an insane rule. This makes "the standard/standard" unusable on the battlefield. You want to shoot an enemy, but your gun says "error, wrong finger". Nah.