-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way log/trace files that are not covered by any layer of a LayeredArchitecture? #222
Comments
I don't think there is a way at the moment. Originally I thought, that the white list way to define layers would draw in all relevant classes in in time anyway. E.g. define layer
|
I think this would by a nice addition, so if anybody is looking for a simple starter to contributions, this here is open for grabs 😉 |
…ll-classes-are-covered
Very nice to see this addition! exactly the thin I tried to test by using something like this
...really hope this gets merged soon !? |
This will add possibilities to ensure that all classes under test are contained within the respective `LayeredArchitecture`/`OnionArchitecture`. It will help users to make sure they don't overlook any classes when defining their architectures. Furthermore, it will help with maintainability of the architectures when new classes are added to the code base later on. In detail the following methods have been added to `LayeredArchitecture` and `OnionArchitecture`: * `ensureAllClassesAreContainedInArchitecture()` * `ensureAllClassesAreContainedInArchitectureIgnoring(packageIdentifiers)` * `ensureAllClassesAreContainedInArchitectureIgnoring(predicate)` Resolves #222
Defining layers and allowed access is easy but how to check if all loaded classes are covered by at least one layer?
The text was updated successfully, but these errors were encountered: