[
https://issues.apache.org/jira/browse/BVAL-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jung updated BVAL-227:
-----------------------------
Description:
As per javadoc for jakarta.validation.constraints.DecimalMin,
jakarta.validation.constraints.DecimalMax:
* Supported types are:
* <ul>
* <li>{@code BigDecimal}</li>
* <li>{@code BigInteger}</li>
* <li>{@code CharSequence}</li>
* <li>{@code byte}, {@code short}, {@code int}, {@code long}, and their
respective
* wrappers</li>
* </ul>
Right now we only validate String. For jakarta.validation.constraints.Min,
jakarta.validation.constraints.Max this is new in Validation 4.0 but doesn't
hurt to have this in 3.1.x IMO
was:
As per javadoc for jakarta.validation.constraints.Min,
jakarta.validation.constraints.Max, jakarta.validation.constraints.DecimalMin,
jakarta.validation.constraints.DecimalMax:
* Supported types are:
* <ul>
* <li>{@code BigDecimal}</li>
* <li>{@code BigInteger}</li>
* <li>{@code CharSequence}</li>
* <li>{@code byte}, {@code short}, {@code int}, {@code long}, and their
respective
* wrappers</li>
* </ul>
Right now we only validate String
> Bultin Min/Max validators should validate against CharSequence
> --------------------------------------------------------------
>
> Key: BVAL-227
> URL: https://issues.apache.org/jira/browse/BVAL-227
> Project: BVal
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Markus Jung
> Assignee: Markus Jung
> Priority: Major
> Fix For: 3.1.1, 4.0.0
>
>
> As per javadoc for jakarta.validation.constraints.DecimalMin,
> jakarta.validation.constraints.DecimalMax:
> * Supported types are:
> * <ul>
> * <li>{@code BigDecimal}</li>
> * <li>{@code BigInteger}</li>
> * <li>{@code CharSequence}</li>
> * <li>{@code byte}, {@code short}, {@code int}, {@code long}, and their
> respective
> * wrappers</li>
> * </ul>
> Right now we only validate String. For jakarta.validation.constraints.Min,
> jakarta.validation.constraints.Max this is new in Validation 4.0 but doesn't
> hurt to have this in 3.1.x IMO
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
