-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Support Jakarta Nonnull/Nullable annotations #3346
Comments
You mixed up two different thinks. Apart from that, I agree that Jakarta annotations should be directly supported. |
That config property will solve my issue, thanks for your swift reply! But it would be nice if this is an automatic one since many frameworks (spring-boot 3 for example) switched to Jakarta. I don't want to be a smart*ss, but technically the builder code is generated code, the sample I posted was generated by I read something about the So for other people running into this issue, add this to your config:
|
Available on edge. |
I ran into an issue with using Jakarta's
@Nullable
instead of javax (or checker).I tried to add the config property :
And it seems to partially work (e.g. for return values), but when using
@Builder
the@Nullable
is not copied to the parameter of the generated methodfirst()
on the Builder.I'd expect
as a builder method, but currently the
@Nullable
is not copied (it does work forjavax
andcheckerframework
as expected)Not sure if it's important, but if I use the javax or checker annotations the
@Nullable
is copied, even whenlombok.addNullAnnotations
has the custom value mentioned above. So it seems some annotations are copied by default, regardless of the value oflombok.addNullAnnotations
The text was updated successfully, but these errors were encountered: