Skip to content

Make Min/Max constraints to be applicable to the string representation of the number #301

Description

@marko-bekhta

Currently, Min/Max constraints are applicable to various integer types and BigDecimal:

* Supported types are:
* <ul>
* <li>{@code BigDecimal}</li>
* <li>{@code BigInteger}</li>
* <li>{@code byte}, {@code short}, {@code int}, {@code long}, and their respective
* wrappers</li>
* </ul>
* Note that {@code double} and {@code float} are not supported due to rounding errors
* (some providers might provide some approximative support).

while at the same time, the TCK has a test for a string representation of these numbers. Since all known implementations (BVal, Hibernate Validator) have been passing the TCK without the exclusion of this test, let's include the string representation in the constraint definition.

Activity

  1. marko-bekhta commented on Oct 6, 2025

    @marko-bekhta
    MemberAuthor

    this idea came from a question on a TCK test: jakartaee/validation-tck#194

  2. changed the title [-]Make Min/Max constraits to be applicable to the string representation of the number[/-] [+]Make Min/Max constraints to be applicable to the string representation of the number[/+] on Oct 13, 2025
  3. added a commit that references this issue on Oct 13, 2025
  4. added a commit that references this issue on Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    EE12Jakarta EE12 release related

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions