[TAPESTRY-2352] Client side validation does not enforce the format of input (i.e., that numeric fields contain numbers)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.11
• Fix Version/s: 5.0.15
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 12/Apr/08 15:21
• Updated: 26/Aug/08 21:40
• Resolved: 26/Aug/08 21:40

Description

So there really should be additional validators that enforce the format of the input, before passing it "down the line" to validators such as Tapestry.Validator.min.

However, there's another issue: we need a way to define a "valid value" for a field in an extensible way; basically so that value that are valid on the server can be passed through. Example: I have a client that wants users to enter "NA" into numeric fields for which they have no data. I don't want the client validation to claim that "NA" is an invalid numeric value, so there needs to be a way to define strings or REs on the client side that are valid and ignored (and passed up the server unchanged).