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
When it comes to validating the annotated classes, JMoleculesDddRules fails to catch the violation for an aggregate referencing a Collection of other aggregates as shown below:
PS: this works ok for the interfaces, and only fails with the annotations. Also, I believe it can be interesting to have that same test/assertions run against two set of objects (one using the interfaces and its equivalent that uses annotations).
If the project is open for contributions, I wouldn't mind looking into it.
Later edit: This rule also seems to be skipped when it comes to annotated objects: Aggregates only refer to entities that are declared to be part of it.
odrotbohm
changed the title
JMoleculesDddRules fails to catch violation for annotated classes
ArchUnit verification fails for annotated aggregate references as collection elements
Aug 29, 2024
When it comes to validating the annotated classes, JMoleculesDddRules fails to catch the violation for an aggregate referencing a Collection of other aggregates as shown below:
Reproduced in tests, here.
PS: this works ok for the interfaces, and only fails with the annotations. Also, I believe it can be interesting to have that same test/assertions run against two set of objects (one using the interfaces and its equivalent that uses annotations).
If the project is open for contributions, I wouldn't mind looking into it.
Later edit: This rule also seems to be skipped when it comes to annotated objects: Aggregates only refer to entities that are declared to be part of it.
Example here:
I have added these failing test cases to my branch and created PR (#254) for visibility:
#254
The text was updated successfully, but these errors were encountered: