[TAP5-1318] Client Pattern constraint validator does not work correctly

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 5.2.1
• Component/s: tapestry-beanvalidator
• Assignee: Unassigned
• Reporter: Vladimir Velikiy
• Created: 20/Oct/10 12:57
• Updated: 20/Oct/10 13:46
• Resolved: 20/Oct/10 13:46

Description

Error object field name for parameter spec in tapestry-beanvalidator.js (spec.pattern in place of spec.regexp):

currently in 5.2.1 version:

Tapestry.Validator.pattern = function(field, message, spec)
{
Tapestry.Validator.regexp(field, message, spec.pattern);
};

must be:

Tapestry.Validator.pattern = function(field, message, spec)
{
Tapestry.Validator.regexp(field, message, spec.regexp);
};

Issue Links

• duplicates: TAP5-1297 Client-side validation of @Pattern is broken