Tapestry
  1. Tapestry
  2. TAPESTRY-2206

Tapestry should have a different data type for numbers than for strings

    Details

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

      Description

      Currently, String and all Number types are lumped together because they use the same component, a TextField.

      However, it is reasonable that they should be differentiated; for example, numeric fields will typically be styled to right justify the fields, whereas text fields are typically left justified.

      Numbers should be data type "number" and have their own edit and display blocks.

        Activity

        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Summary Tapestry should have a different date type for numbers than for strings Tapestry should have a different data type for numbers than for strings
        Howard M. Lewis Ship made changes -
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Fix Version/s 5.0.11 [ 12312968 ]
        Mark Thomas made changes -
        Workflow jira [ 12424733 ] Default workflow, editable Closed status [ 12568559 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568559 ] jira [ 12591602 ]

          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