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
TBH I'm not quite sure if this change is not against DDD rules, but I have the following problem. Given the following class...
@RequiredArgsConstructor
@Getter
public class MyAggregateRoot implements AggregateRoot<MyAggregateRoot, UUID> {
@Identity
private final UUID id;
private MyInnerClass myInnerClass;
@RequiredArgsConstructor
@Getter
public class MyInnerClass implements ValueObject {
private final String param;
}
}
Having this class and checking it with org.jmolecules.archunit.JMoleculesDddRules#valueObjectsMustNotReferToIdentifiables leads to the violation that MyInnerClass.this$0 refers to an Identifiable. This - of course - is correct in the first place. But I'm asking myself if it would be ok in this case to ignore the synthetic field to the outer class (MyInnerClass.this$0) from this check.
The text was updated successfully, but these errors were encountered:
TBH I'm not quite sure if this change is not against DDD rules, but I have the following problem. Given the following class...
Having this class and checking it with
org.jmolecules.archunit.JMoleculesDddRules#valueObjectsMustNotReferToIdentifiables
leads to the violation thatMyInnerClass.this$0
refers to an Identifiable. This - of course - is correct in the first place. But I'm asking myself if it would be ok in this case to ignore the synthetic field to the outer class (MyInnerClass.this$0
) from this check.The text was updated successfully, but these errors were encountered: