Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add maxWarnings CLI option #568

Merged
merged 3 commits into from
Apr 17, 2016
Merged

Add maxWarnings CLI option #568

merged 3 commits into from
Apr 17, 2016

Conversation

house9
Copy link
Contributor

@house9 house9 commented Mar 10, 2016

Exit with non-zero value when the number of warnings is greater than the maxWarning option.

see #567

DCO 1.1 Signed-off-by: Jesse House jesse.house@codingzeal.com

Exit with non-zero value when the number of warnings is greater than the maxWarning option.
Easily fail CI builds without needing to update all sass-lint rules to errors.

Usage: `sass-lint --max-warnings 0 -c sass-lint.config.yml sass/**/*.scss`

This closes sasstools#567

Based on the eslint maxWarnings CLI option:

* http://eslint.org/docs/user-guide/command-line-interface#options
@DanPurdy
Copy link
Member

Thanks, I'll have a look over this later 👍

closes #567

@DanPurdy
Copy link
Member

DanPurdy commented Apr 5, 2016

Hi @house9 Sorry for the delay here, we just finally merged all of our 1.6 work into develop which will cause a few conflicts for this PR. Would you mind updating it now and then we can look to get it merged in.

Thanks! 👍

  # Conflicts:
  #	tests/cli.js
@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.871% when pulling 07b6e69 on house9:max-warnings into db4db51 on sasstools:develop.


return warningCount > 0 && warningCount > program.maxWarnings;
};

var detectPattern = function (pattern) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@house9
Copy link
Contributor Author

house9 commented Apr 5, 2016

@DanPurdy merge conflicts have been resolved, Thanks.

@DanPurdy
Copy link
Member

@house9 sorry for the delay here. This looks good to me, if you could update with the latest progress from develop then we can merge this in. Thanks! 👍

@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.871% when pulling 4cfcc6b on house9:max-warnings into 9fa414d on sasstools:develop.

@DanPurdy DanPurdy merged commit d24068b into sasstools:develop Apr 17, 2016
@DanPurdy DanPurdy added this to the 1.6.0 - Latest Gonzales milestone Apr 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants