mapstruct / mapstruct/mapstruct-idea
Renaming a @Getter annotated field results in a getter inside the mapping definition (instead of the new field name)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 168
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
```Java
public class User {
String name;
}
@Mapper
public interface UserMapper {
@Mapping(source="name", target="nom")
UserDto toDto(User user)
}
```
When you rename User.name to lastName, the mapping becomes `@Mapping(source="getLastName", target="nom")`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the rename from User.name to lastName in the User and UserMapper example, focusing on how @Getter fields are resolved in the mapping definition. Trace the rename handling and verify that the mapping references the renamed field rather than a generated getter name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100