steering

Only show style errors of things that have changed since master. This support tools that support exporting output in checkstyle format. This can be useful if you want to convert a project gradually towards a new config, (e.g. adding a new rule from the latest release of your linter). Another case were this is beneficial is were you do not want to break a build when updating the linter.

Installation

npm install --save-dev @relekang/steering

Usage

You can use this in two different ways, either by reading files or reading from stdin.

Reading from files

steering checkstyle-report.xml

Reading from stdin

cat checkstyle-report.xml | steering

# example usage with eslint
eslint . -f checkstyle | steering

Contributing

Firstly, all contributions is super appreciated :sparkles:

As you may have noticed, this repository has no issues here on Github. There is a trello board with planned features and such. If you have questions, bug report or feature requests you are encouraged to drop by our gitter channel and say hi. If you are comfortable with it bug reports in form of a pull-request with a broken test would be awesome. Unsure about where the test belong? Then create a new file in the test folder with your test. Unsure about how to do create a pr? You can check out How to create a Pull Request on GitHub, a video tutorial by @kentcdodds or drop by the gitter channel and ask for help.