Add extension support #18
Merged
Conversation
This file contains 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
…ies basic constraints, like unique identifier
…rties, by prefixing them with 'extension.${extension-id}'
…d guard, that only enabled extensions (extension.${my-extension}.enabled=true) are called on rule evaluation.
codecholeric
force-pushed
the
add-extension-support
branch
from
426b9bf
to
ab90332
Compare
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.
This PR adds some basic extension support to ArchUnit. In particular it's now possible, to register any custom
ArchUnitExtensionvia standardServiceLoaderapproach, and have ArchUnit forward evaluated rules to all those registered extensions, before failing any test because of rule violations.This should in particular be a nice interface to plug in some visualization, e.g. to export classes and evaluated violations to some other format to display.