You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it is possible to validate that certain classes must call a specific method from another class using the following rule:
@ArchTest
public final ArchRule classShouldCallAudit = ArchRuleDefinition.classes().that()
.areAnnotatedWith(Transactional.class).should()
.callMethod(Audit.class, "audit", String.class, String.class)
.as("Ensure system audit");
It would be interesting to add the same possibility to methods, using something similar to:
@ArchTest
public final ArchRule methodShouldCallAudit = ArchRuleDefinition.methods().that()
.areAnnotatedWith(Transactional.class).should()
.callMethod(Audit.class, "audit", String.class, String.class)
.as("Ensure system audit");
The text was updated successfully, but these errors were encountered:
Currently, it is possible to validate that certain classes must call a specific method from another class using the following rule:
It would be interesting to add the same possibility to methods, using something similar to:
The text was updated successfully, but these errors were encountered: