Client side validation does not enforce the format of input (i.e., that numeric
fields contain numbers)
-------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2352
URL: https://issues.apache.org/jira/browse/TAPESTRY-2352
Project: Tapestry
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.11
Reporter: Howard M. Lewis Ship
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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
