Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-12381

DatePatternConstraint and BasicDatePatternConstraint allow dates that do not exist

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.4
    • Fix Version/s: 2.5
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      The date 04/31/2014 is allowed but not 04/32/2014. This is an issue for the date picker and non date picker fields since you can change the date picker field after choosing your date.

      Can be tested in KRAD component library, validation → Date Constraint,

        Attachments

          Issue Links

            Activity

            Hide
            matthew.wuertz Matthew Wuertz (Inactive) added a comment -

            Per Jerry, this should be covered by server-side validation. The client-side validation is for the format only (is it ##/##/####), not validating specific values beyond simple checks, like 32 days in a month. The type of regular expression required for validating that the days in a specific month (along with leap year considerations) is overly complex. Instead, when the value is submitted to the server, it will be checked there. But the purpose of the demo mentioned in this defect is only for client-side format validation (there is no submission to the server).

            Show
            matthew.wuertz Matthew Wuertz (Inactive) added a comment - Per Jerry, this should be covered by server-side validation. The client-side validation is for the format only (is it ##/##/####), not validating specific values beyond simple checks, like 32 days in a month. The type of regular expression required for validating that the days in a specific month (along with leap year considerations) is overly complex. Instead, when the value is submitted to the server, it will be checked there. But the purpose of the demo mentioned in this defect is only for client-side format validation (there is no submission to the server).
            Hide
            cniesen Claus Niesen added a comment -

            It was decided that client side validation will not cover advanced validation like leap years. Only basic validations such as size and format is done on client side.

            Show
            cniesen Claus Niesen added a comment - It was decided that client side validation will not cover advanced validation like leap years. Only basic validations such as size and format is done on client side.

              People

              • Assignee:
                matthew.wuertz Matthew Wuertz (Inactive)
                Reporter:
                shahess Shannon Hess
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: