Closed thekiwi closed 7 years ago
Thanks for the report, the bug only concerns assertions checking on submodels. I found how to fix it but won't be able to push a new release before next week.
Fixed in 2.5.4 :+1: Thanks !
@sylvainpolletvillard Thank you!
I am finding that ObjectModel ignores the validations of sub-objects in a model.
Take this example:
Here's the output I'm getting:
When you run this, you can see that
validation check result:
is output 4 times (with the correct result), which correlates with the 4 calls to.validate(...)
however only the second call actually causes errors. It seems the Order.validate ignores the validation of the sub-object.Is this expected behaviour, or a bug? If it is expected, is there a way to enforce an object validation validates all the child model as well?