You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this with CharSequence, but there may be others. The Validation spec uses CharSequence as a type for validation because it covers String, StringBuffer, StringBuilder, and others. Anywhere the spec allows CharSequence we should allow its implementing types.
In some cases, such as @DecimalMax which allows CharSequence, we are currently indicating that String is not a valid Type for the annotation, even though it is.
Specification:
Jakarta Validation
Type of language feature proposed:
Select all that apply
diagnostic
quick-fix
snippet
other, please specify:
The text was updated successfully, but these errors were encountered:
Description:
I noticed this with
CharSequence
, but there may be others. The Validation spec usesCharSequence
as a type for validation because it coversString
,StringBuffer
,StringBuilder
, and others. Anywhere the spec allowsCharSequence
we should allow its implementing types.In some cases, such as
@DecimalMax
which allowsCharSequence
, we are currently indicating thatString
is not a valid Type for the annotation, even though it is.Specification:
Jakarta Validation
Type of language feature proposed:
Select all that apply
The text was updated successfully, but these errors were encountered: