Robert Hicks wrote:
>
> dependencies => {
> "project_names" => {
> "ICGS LIMS Help Desk Tickets" => { task_names =>
> qr/^\d{9}$/, },
> },
> },
This is an incorrect way to specify dependencies. You could patch DFV to
throw an error in this case if you'd like. The docs for 'dependencies'
are below for reference.
Dependencies are only for expressing conditional requiredness.
Constraints are always expressed separately.
Mark
dependencies => {
# If cc_no is entered, make cc_type and cc_exp required
"cc_no" => [ qw( cc_type cc_exp ) ],
# if pay_type eq 'check', require check_no
"pay_type" => {
check => [ qw( check_no ) ],
}
},
This is for the case where an optional field has other requirements.
The dependent fields can be specified with an array reference.
If the dependencies are specified with a hash reference then the
additional constraint is added that the optional field must equal
a key
for the dependencies to be added.
Any fields in the dependencies list that is missing when the
target is
present will be reported as missing.
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
