the documentation also specifies that the annotation must have target set to TYPE_PARAMETER or TYPE_USE, and mentions org.checkerframework.checker.nullness.qual.Nullable as an example of a suitable annotation for this purpose.
Indeed, if I use ChecherFramework's @Nullable annotation, everything works fine.
If instead I use my own annotation, copied one-to-one from ChecherFramework's @Nullable annotation removing CF's own annotations, the feature stops working. This is my @Nullable annotation:
....sooooo what is it that org.checkerframework.checker.nullness.qual.Nullable has, that my.own.annotation.Nullable is missing in order to work? The only difference seems to be the additional annotations that come from CF's own package, but then is ChecherFramework's @Nullable annotation the only annotation to be used for this feature?
This is similar to #889, but I couldn't find my answer there.
I am trying to generate a TS file from a bunch of Java classes through the
typescript-generator-maven-plugin
.The documentation states that I need to:
<nullableAnnotations>
property<nullabilityDefinition>
propertyfor example:
TYPE_PARAMETER
orTYPE_USE
, and mentionsorg.checkerframework.checker.nullness.qual.Nullable
as an example of a suitable annotation for this purpose.Indeed, if I use ChecherFramework's
@Nullable
annotation, everything works fine.This is ChecherFramework's
@Nullable
annotation, for reference:If instead I use my own annotation, copied one-to-one from ChecherFramework's
@Nullable
annotation removing CF's own annotations, the feature stops working. This is my@Nullable
annotation:and this is the output:
....sooooo what is it that
org.checkerframework.checker.nullness.qual.Nullable
has, thatmy.own.annotation.Nullable
is missing in order to work? The only difference seems to be the additional annotations that come from CF's own package, but then is ChecherFramework's@Nullable
annotation the only annotation to be used for this feature?Thanks, great tool anyway.