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
While testing the JSpecify annotations with NullAway, I thought I would be able to remove the -XepOpt:NullAway:AnnotatedPackages setting in favor of using the @NullMarked annotation. I want to specify the code to be checked on class level instead of package level. This does not seem to be possible right now. Setting the @NullMarked annotation does not have any effect. However, when I remove the AnnotatedPackages setting NullAway even fails to initialize at all.
Will this be fixed in a future release to provide conformity with the JSpecify specification?
The text was updated successfully, but these errors were encountered:
Just a sidenote: I think both variants should work at the same time.
In my codebase, it is not feasable to add NullMarked everywhere, therefore I enjoyed using NullAway:AnnotatedPackages. I want to keep doing this :)
While testing the JSpecify annotations with NullAway, I thought I would be able to remove the
-XepOpt:NullAway:AnnotatedPackages
setting in favor of using the@NullMarked
annotation. I want to specify the code to be checked on class level instead of package level. This does not seem to be possible right now. Setting the@NullMarked
annotation does not have any effect. However, when I remove theAnnotatedPackages
setting NullAway even fails to initialize at all.Will this be fixed in a future release to provide conformity with the JSpecify specification?
The text was updated successfully, but these errors were encountered: