Grails

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.1
• Fix Version/s: 1.0.2
• Component/s: None
• Labels:

  None

Email constraint still seems too aggressive / has regressed from previous behaviour - I thought we solved this long ago.

Email constraint should never cause a failure if nullable/blank are enabled (for null/blanks as appropriate).

In the email constraint, if the value is null or blank it should just be ignored and nullable/blank left to deal with those failures, otherwise functionality is being duplicated and causes this problem.

• Assignee:

  Graeme Rocher

  Reporter:

  Marc Palmer

• Created:

  19/Mar/08 10:54 AM

  Updated:

  18/May/11 8:38 AM

  Resolved:

  20/Mar/08 10:41 AM