Type Nullability for @NonNullApi for "any other annotation that has the name nullable"

[Pascalmh]

Describe the bug

When NOT using the @NonNullApiHilla will mark properties in the generated typescript interfaces as optional when adding

any other annotation (including custom) that has the name nonnull (case-insensitive).
– https://vaadin.com/docs/latest/hilla/reference/type-nullability

This does not work the other way around, when using the @NonNullApi (https://vaadin.com/docs/latest/hilla/reference/type-nullability#nonnullapi)

And adding this annotation: @org.springframework.lang.Nullable the property will not be marked as optional in the generated typescript interface.

Expected-behavior

any other annotation (including custom) that has the name nullable (case-insensitive) makes the generated property in the typescript interface optional.

Reproduction

• use @NonNullApi
• add the Annotation @org.springframework.lang.Nullable

System Info

Vaadin 24.6.2

[cromoteca]

Support for Spring annotations is added in 24.7. In 24.6 you can use com.vaadin.hilla.Nullable for that. Also note that, while 24.7 supports Spring nullability annotations, JSpecify ones are recommended, as Spring is also going to use JSpecify by default, see spring-projects/spring-framework#28797. Hilla 24.7 also introduces support for JSpecify annotations.

[platosha]

Let's clarify the docs in vaadin/docs#4155.