@PositiveOrZero annotation should not make ts fields not-nullable

[berndhopp]

Describe the bug

The javadoc of @PositiveOrZero says that "null elements are considered valid.". However, the client side validation will not accept null fields.

Expected-behavior

Null values are being accepted on the client-side for fields that are annotated with @PositiveOrZero

Reproduction

Annotate a DTO-Field on the java side with @PositiveOrZero, then bind the client side representation of that field to an vaadin-integer-field in a form. Leave that field empty and call validate() on the binder. The empty value will not be accepted.

System Info

Windows 11, Java 22, Chrome

[cromoteca]

What Java type are you using for that field? Non-nullability can be triggered by using primitive types or by using @NonNullApi annotation in the package.

[platosha]

Seems to be a bug in the form library.

[platosha]

Might be caused by using NaN for internal representation of empty number field state.