Tapestry
  1. Tapestry
  2. TAPESTRY-2352

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

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.11
    • Fix Version/s: 5.0.15
    • Component/s: tapestry-core
    • Labels:
      None

      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).

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development