Tapestry
  1. Tapestry
  2. TAPESTRY-572

NumberValidator should accept Strings

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None

      Description

      Applying NumberValidator to a TextField will allow a number to be validated as a number and stored as a String. However, NumberValidator is not able to take a String and display it as a number. I think this should be a bidirectional process. An example of where this would be useful is the following:

      I'd like to store a number as a String so I don't lose any prepending 0's (which RDBMSs love to throw out) when persisting the data. However, I do want to ensure that only a number is valid input.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Kevin Menard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development