Skip to content

#211 Remove methods should not be considered fluent setters. #212

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jarlesat
Copy link

@jarlesat jarlesat commented Dec 3, 2024

This is a first take on it.

With this change fluent remover's will be ignored when verifying the mapper. A remover (removePassenger) is added to FluentCarDTO as part of the tests.

Tested it with IntelliJ as well and seems to be working as intended, but I would be more than happy for feedback and suggestions.

@hduelme
Copy link
Contributor

hduelme commented Dec 13, 2024

As you mentioned in #211, this depends on mapstruct/mapstruct#3072. To ensure consistency across all versions, the check should only be applied when a MapStruct version is detected in which the issue has been resolved.

@jarlesat
Copy link
Author

Thanks for the feedback. As soon as (and if) mapstruct/mapstruct#3072 is approved and merged, I will update the PR with a suggestion on how to do it. I guess that to extend MapStructVersion and MapstructUtil::resolveMapStructProjectVersion is the way to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants