Custom message not working for Constraint_length

[Martimiz]

Although the constraint is set to data-parsley-maxlength / data-parsley-minlength / data-parsley-length correctly,
the message uses data-parsley-max-message / data-parsley-min-message / data-parsley-range-message /

This is because the message attribute is based on Constraint::getConstraintName(), and that is set to min/max/range in Constraint_length, Constraint_check and Constraint_value, where only the last one is correct.

If range/max/min is to be kept in place for all three constraints, then a solution could be to either

• enable some sort of mapping the constraintname to the proper parsley constraintname.
• move the message attribute construction from ZenValidatorConstraint::applyParsley() to the applyParsley() function in each module

Happy to create a pull request, if you agree on one of these options (or something else)

Martine

[lekoala]

Maybe we could just have a function "setCustomMessage" called in applyParsley with a default behaviour and override when necessary ?