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
I'd also love to support a mythical NullableApi and NullableFields obviously saying the inverse is the default... I say mythical, but making my own annotations, but they're really only good if something supports them.
Maybe to add on to this, a setting(? or additional ep rule) that requires you to have one or the other defined.
The text was updated successfully, but these errors were encountered:
Hi @xenoterracide NullAway already assumes everything is @NonNull by default, so I'm not sure what would be required to additionally support these annotations. Do you have an example you're thinking of?
To be honest I'm not sure how well they're supported outside of spring, and with all the talk around jspecify, that I only found out about 4 days ago, probably shortly after creating this. Probably not worth the conversation. Really it's all around the problem of "all tools aren't making the same assumptions as to what the defaults are, and so we still have to set both annotations on everything"
So after reading https://github.com/uber/NullAway/wiki/Supported-Annotations I'm assuming that the
@NonNullApi
andNonNullFields
aren't in any way supported (they're spring)? https://www.baeldung.com/spring-null-safety-annotations if they aren't could they be?I'd also love to support a mythical
NullableApi
andNullableFields
obviously saying the inverse is the default... I say mythical, but making my own annotations, but they're really only good if something supports them.Maybe to add on to this, a setting(? or additional ep rule) that requires you to have one or the other defined.
The text was updated successfully, but these errors were encountered: