Replies: 1 comment
-
yeah - I'm OK with that. In fact, I thought that I'd done that already. But, a PR (or new issue) would be appreciated. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
A common way to manage nullability annotations is to put a default @nonnull annotation at method / parameter / field level using package-info.java and then only add @nullable where relevant. Rational being that it is far more common to want something @nonnull than @nullable.
The idiomatic way to do it is to define an annotation like that
And then apply it to the package-info.java:
It tried to define a such annotation for record components and apply it. But record-builder seems to not care.
I have not yet dug into record-builder internals; is there a chance to be able to use this pattern with record-builder?
Beta Was this translation helpful? Give feedback.
All reactions