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
{{ message }}
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.
If an interface uses a type from a different Java package (using @extern foo.yaml), the output will be @annotation fully.qualified.ClassName, which causes Java compilation problems.
For example:
public abstract io.grpc.Status send(Id recipient, @nullable com.google.package.Message message);
Results in:
error: scoping construct cannot be annotated with type-use annotation: @org.checkerframework.checker.nullness.qual.Nullable
Not a Java expert, but I think the correct way to apply the annotation is:
com.google.package.@nullable Message
The text was updated successfully, but these errors were encountered:
--java-nullable-annotation org.checkerframework.checker.nullness.qual.Nullable
If an interface uses a type from a different Java package (using @extern foo.yaml), the output will be @annotation fully.qualified.ClassName, which causes Java compilation problems.
For example:
public abstract io.grpc.Status send(Id recipient, @nullable com.google.package.Message message);
Results in:
error: scoping construct cannot be annotated with type-use annotation: @org.checkerframework.checker.nullness.qual.Nullable
Not a Java expert, but I think the correct way to apply the annotation is:
com.google.package.@nullable Message
The text was updated successfully, but these errors were encountered: