Closed heston closed 8 years ago
Working as intended. Warnings shouldn't fail the build. They're informational. This is also how the ESLint CLI works. If you disagree, I suggest taking it up on the ESLint issue tracker first: https://github.com/eslint/eslint/issues
Currently, this task returns
true
when there are lint warnings, andquiet
is set to false. This makes it difficult to fail a build in a CI environment for warnings. This PR makes it possible for Grunt to return a non-0 exit code when lint warnings are present.If
opts.quiet
is set tofalse
(default), then this task will returnfalse
if there are any errors or warnings. Ifopts.quiet
istrue
, then this task will only returnfalse
if there are errors.