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 don't think we can fix this on our end. We just provide elements that can be renamed in the MapstructSourceTargetParameterRenameHandler. How those parameters are used by the PsiElementRenameHandler is beyond our control. At least to my knowledge.
thunderhook
changed the title
Fields are renamed with getter
Renaming an @Getter annotated field results in a getter inside the mapping definition (instead of the new field name)
May 23, 2024
thunderhook
changed the title
Renaming an @Getter annotated field results in a getter inside the mapping definition (instead of the new field name)
Renaming a @Getter annotated field results in a getter inside the mapping definition (instead of the new field name)
May 23, 2024
Thanks for the analysis @thunderhook. I'm also not sure what we can do. Perhaps this is some kind of a bug in the Lombok plugin. It works correctly when renaming a field (which triggers method rename) and renaming the getter directly
When you rename User.name to lastName, the mapping becomes
@Mapping(source="getLastName", target="nom")
The text was updated successfully, but these errors were encountered: