Adaptations for 4.7.0 #45
Conversation
Improve handling of @Assert on associations Use $now as default for Date again
|
|
||
| Customer @assert: (case | ||
| when Customer is null then 'Customer must be specified' | ||
| when Customer is null then null // handled by @mandatory |
There was a problem hiding this comment.
do we need this check as the next line when not exists Customer then Customer does not exist` would cause an issue?
There was a problem hiding this comment.
No, as indicated by the comment, the null check is also handled by a @mandatory annotation. Checking null here again leads to duplicate error messages: One from the @mandatory validation and one from the @assert validation.
There was a problem hiding this comment.
I think that´s clear. But I´m wondering why we cannot simply skip the null check here. Am I correct that if we don´t have an early exit in the case statement, the when not exists Customer then Customer does not exist would also cause a second message,?
There was a problem hiding this comment.
Ah now I understand. Yes the when not exists Customer is also true if Customer is not set (aka null).
2 participants
Uh oh!
There was an error while loading. Please reload this page.