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
Custom validation should have a path like standard validation.
Actual Behaviour
Custom validation have incomplete proprety path.
I have an object Flow with a list of Tasks.
If I have an invalid Log task with an empty message property annotated with @NonEmpty, it gives me the following property path: tasks[0].message.
But if I have an invalid Dag task validated by a custom validator (with @Dag) then it gives me the following property path: tasks which is incorrect as I should have tasks[0].tasks as it's the property tasks of the Dag object that is invalid, and the Dag is the first item of the list tasks of the Flow object. validation-superbuilder-issue.zip
A reproducer project with a test with both examples is provided here:
Steps To Reproduce
No response
Environment Information
No response
Example Application
No response
Version
4.0.5
The text was updated successfully, but these errors were encountered:
Expected Behavior
Custom validation should have a path like standard validation.
Actual Behaviour
Custom validation have incomplete proprety path.
I have an object Flow with a list of Tasks.
If I have an invalid Log task with an empty
message
property annotated with@NonEmpty
, it gives me the following property path:tasks[0].message
.But if I have an invalid Dag task validated by a custom validator (with
@Dag
) then it gives me the following property path:tasks
which is incorrect as I should havetasks[0].tasks
as it's the propertytasks
of the Dag object that is invalid, and the Dag is the first item of the listtasks
of the Flow object.validation-superbuilder-issue.zip
A reproducer project with a test with both examples is provided here:
Steps To Reproduce
No response
Environment Information
No response
Example Application
No response
Version
4.0.5
The text was updated successfully, but these errors were encountered: