I'm running the log reporter followed by the fail reporter, and unexpectedly, the fail reporter is failing on warnings:
[10:08:03] PHP Code Sniffer found a problem in C:\Users\Tim\Dropbox\Chromatix\htdocs\base\theme-portal\inc\portal-setup.php
FILE: ...\Dropbox\Chromatix\htdocs\base\theme-portal\inc\portal-setup.php
----------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
----------------------------------------------------------------------
10 | WARNING | Inline comments must start with a capital letter
| | (Squiz.Commenting.InlineComment.NotCapital)
----------------------------------------------------------------------
Time: 817ms; Memory: 10Mb
C:\Users\Tim\Dropbox\Chromatix\htdocs\base\gulp-tasks\node_modules\longjohn\dist\longjohn.js:192
throw e;
^
Error: PHP Code Sniffer failed on
C:\Users\Tim\Dropbox\Chromatix\htdocs\base\theme-portal\inc\portal-setup.php
I'm not sure if this is intended behaviour or not. I'm assuming it's not - but if it is, would it be possible to have an optional flag to only fail on errors?
I'm running the
logreporter followed by thefailreporter, and unexpectedly, the fail reporter is failing on warnings:I'm not sure if this is intended behaviour or not. I'm assuming it's not - but if it is, would it be possible to have an optional flag to only fail on errors?