PR #892 merged for release 5.5.1 fixed an issue where cardinality constraints on RelationshipFrom objects were not properly checked, and never raised violations.
While this is good and necessary, it can lead to a lot of side effects for applications where the relationships were not properly defined, and it suddenly starts throwing a lot of violations.
This is of course healthy, because you should not have been able to bypass cardinality constraints in the first place ; but that change should also not have been implemented in a minor release, and without a warning about the potential for breaking (my apologies).
To counter this, we had the idea of introducing a soft cardinality check, instead of a strict violation Exception ; this could be enabled by default for now to avoid unexpected breaking changes, and then switched in the next major release, with a proper warning.
Note : This should only apply to the newly fixed check (RelationshipFrom) ; otherwise we stop throwing violations for the ones that previously worked (RelationshipTo), which is a bigger problem. In the next major release, we can make it uniform.
cc @billycalladine
PR #892 merged for release 5.5.1 fixed an issue where cardinality constraints on RelationshipFrom objects were not properly checked, and never raised violations.
While this is good and necessary, it can lead to a lot of side effects for applications where the relationships were not properly defined, and it suddenly starts throwing a lot of violations.
This is of course healthy, because you should not have been able to bypass cardinality constraints in the first place ; but that change should also not have been implemented in a minor release, and without a warning about the potential for breaking (my apologies).
To counter this, we had the idea of introducing a soft cardinality check, instead of a strict violation Exception ; this could be enabled by default for now to avoid unexpected breaking changes, and then switched in the next major release, with a proper warning.
Note : This should only apply to the newly fixed check (RelationshipFrom) ; otherwise we stop throwing violations for the ones that previously worked (RelationshipTo), which is a bigger problem. In the next major release, we can make it uniform.
cc @billycalladine