Enable 3rd party to handle violations #16
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 adds an API for 3rd party clients to access information about violations.
Up to now,
rule.evaluate(classes)
didn't give a lot of useful information to react to violations, e.g. for drawing some kind of external report, etc.Now it's possible to react to certain types of objects, contributing to a violation, like
JavaFieldAccess
, etc.The first draft of the API can be used the following way
The handler will be notified about all objects of an assignable type, i.e.
ViolationHandler<JavaAccess<?>>
will be notified about all violations anyJavaAccess
contributed to,ViolationHandler<JavaMethodCall>
will only be notified about violations caused by method calls.