Closed reidab closed 1 year ago
@reidab Thank for your contribution 👍
Before merging, please fix CI builds in your PR 🙏
Okay, that should be cleaned up now.
🚀 [bumpr] Bumped! New version:v2.3.3 Changes:v2.3.2...v2.3.3
Hi, @reidab! We merged your PR to reviewdog! 🐶 Thank you for your contribution! ✨
We just invited you to join the @reviewdog organization on GitHub. Accept the invite by visiting https://github.com/orgs/reviewdog/invitation. By joining the team, you'll be a part of reviewdog community and can help the maintenance of reviewdog.
Thanks again!
RuboCop's severity levels are represented by
RuboCop::Cop::Severity
objects, not symbols. Internally, this objects holds a symbol in itsname
attribute an implements comparison methods.Sadly, these comparisons aren't reversable:
severity === :info => true
, but:info === severity => false
.The ruby case statement performs tripple-equals comparisons with the argument to the
when
clause as the first operand, so the existing case statement always returnedUNKNOWN_SEVERITY
.In addition to fixing the above issue, this PR adds mappings for the non-standard RuboCop
convention
andrefactor
severity levels toINFO
and calculates a top-levelseverity
value in the rdjson output based on RuboCop's configured fail level.Fixes #75