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
In the version of lombok-pg I'm using (0.11.3), Builder will allow fields which are marked @NonNull to be initialized to null, as demonstrated below. If possible, I think Builder should do a runtime check to ensure that the object passed in is indeed not null, just like @Setter does.
I am aware of a similar-sounding issue, #54. However that issue seems to indicate that fields marked @NonNull should be mandatory fields (just like final fields), but does not mention that the Builder should actually do the null check.
The text was updated successfully, but these errors were encountered:
In the version of lombok-pg I'm using (0.11.3),
Builder
will allow fields which are marked@NonNull
to be initialized tonull
, as demonstrated below. If possible, I thinkBuilder
should do a runtime check to ensure that the object passed in is indeed not null, just like@Setter
does.I am aware of a similar-sounding issue, #54. However that issue seems to indicate that fields marked
@NonNull
should be mandatory fields (just likefinal
fields), but does not mention that theBuilder
should actually do the null check.The text was updated successfully, but these errors were encountered: