Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Renaming a @Getter annotated field results in a getter inside the mapping definition (instead of the new field name)

Open
#197 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

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.

Description

help wanted
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")

Dominant language
Java
Stars
168
Forks
41
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapstruct/mapstruct-idea

All issues in mapstruct/mapstruct-idea

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.