Add a git-ratchet formatter

The version of ESLint you are using. Any

The problem you want to solve. I want to use ESLint to report on problems in my existing codebase and am fine with existing violations existing, however I would like to prevent additional violations from being added to the codebase.

For example, I would like to enable the “semi” rule so that semicolons are required, and currently have 100 violations in the codebase. However if someone adds a line of code without a semicolon so that there are now 101 violations, I would like my CI build to fail.

Your take on the correct solution to problem. git-ratchet can be used to keep track of measures in a codebase, it can then report that a metric has increased and a CI build can be failed.

Its reporting format is very simple: rule-name,N where N is the number of violations for that metric.

e.g.:

semi,100
curly,8
comma-dangle,19

Note that this reports on total violations found, not on violations per file.

Are you willing to submit a pull request to implement this change? Yes, I’d just like to gauge the interest and suitability.

[platinumazure]

I don’t think we’re likely to accept new formatters at this point unless there’s a clear need for it in order for ESLint to work with popular integrations. Others on the team might disagree, though.

As noted, you can publish the formatter to npm and then others can still get the benefit. 😄

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.