refactor: Add facade around AnalyzerMessage #163
Merged
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.
This is a follow-up on #162, and depends on it.
Don't review this until #162 i smerged, I will fix the commit history.This PR extracts the previously internal
SoraldAbstractProcessor.Bug
class into a separatesorald.sonar.RuleViolation
class, which is just a thin facade aroundorg.java.sonar.AnalyzerMessage
. Depending on how we proceed with #156, we may not have access to the actualAnalyzerMessage
(but some higher-level abstraction instead), and so this PR is a precaution.Since the facade was essentially already there in form of the Bug class, this change was very little effort, and also coincidentally cleans up some of the code base. With this change, the only sonar internals we touch in sorald are the check classes, but it doesn't seem reasonable at the moment to put adapters around them. I think we'll leave them be.