Expose ArchUnit predicate resideInLayer #179
Open
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
rweisleder
commented
Mar 23, 2023
| * <pre> | ||
| * classes().that(resideInLayer(DomainLayer.class))... | ||
| * | ||
| * classes().that(...).should(ArchCondition.from(resideInLayer(DomainLayer.class)))... |
There was a problem hiding this comment.
Unfortunately, we can't just add another method ArchCondition<JavaClass> resideInLayer(Class<? extends Annotation> annotation) to be able to write classes().should(resideInLayer(DomainLayer.class)). 🤔 Maybe you have a better idea?
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 resolves the initial requirement mentioned in #100.
I'm not sure, if we should also expose predicates for DDD types, like
types.that(areValueObjects()). If so, I'd create an additional PR.