Accept unknown perlcritic violations & use severity from perlcritic report #139
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
otrosien
force-pushed
the
unknown-perlcritic-rules
branch
from
8f1cf12 to
8b2a480
Compare
Closed
otrosien
changed the title
|
Kudos, SonarCloud Quality Gate passed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unknown perlcritic violations are treated as "external issues" of type "code smell". I would have converted all perlcritic violations to external issues, but then we lose the issue type (bug, code-smell, etc) as we don't get those from the perlcritic report.
This change also introduces the mapping of the severity levels 1-5 of the report to the severity levels INFO-BLOCKER of SonarQube.