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
When using record-builder with nullaway, the record-builder approach of keeping field annotations works nicely for nullable fields. In our code base, we often use fields wrapped with Optional instead of nullable fields though, which of course don't have a @Nullable annotation. This causes issues when enabling the option addConcreteSettersForOptional for nullable convenience setters, as those don't have a @Nullable annotation either (which nullaway then complains about). It would be great if we could provide the nullability annotation to use for such cases via the config and then have it on the generated setters.
The text was updated successfully, but these errors were encountered:
When using record-builder with nullaway, the record-builder approach of keeping field annotations works nicely for nullable fields. In our code base, we often use fields wrapped with
Optional
instead of nullable fields though, which of course don't have a@Nullable
annotation. This causes issues when enabling the optionaddConcreteSettersForOptional
for nullable convenience setters, as those don't have a@Nullable
annotation either (which nullaway then complains about). It would be great if we could provide the nullability annotation to use for such cases via the config and then have it on the generated setters.The text was updated successfully, but these errors were encountered: