Skip to content

#1216 Pick candidate method with most specific return type - #2993

Merged
filiphr merged 5 commits into
mapstruct:mainfrom
filiphr:1216
Oct 2, 2022
Merged

#1216 Pick candidate method with most specific return type#2993
filiphr merged 5 commits into
mapstruct:mainfrom
filiphr:1216

Conversation

@filiphr

@filiphr filiphr commented Aug 28, 2022

Copy link
Copy Markdown
Member

When there are multiple candidate methods returning different types.
We should be able to use the method with the most specific return type (if such a method exists)

Fixes #1216

When there are multiple candidate methods returning different types.
We should be able to use the method with the most specific return type (if such a method exists)
Comment thread processor/src/test/java/org/mapstruct/ap/test/bugs/_2840/Issue2840Test.java Outdated
@sjaakd

sjaakd commented Sep 4, 2022 via email

Copy link
Copy Markdown
Contributor

@filiphr

filiphr commented Sep 26, 2022

Copy link
Copy Markdown
Member Author

I've removed the test cases we had for #2840 from this PR since the actual fix for that is in #3032. This PR is only adding a new feature

@sjaakd

sjaakd commented Oct 1, 2022

Copy link
Copy Markdown
Contributor

General mechanism LGTM. One question though..

@filiphr
filiphr merged commit 266c5fa into mapstruct:main Oct 2, 2022
@filiphr
filiphr deleted the 1216 branch October 2, 2022 17:20
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.

Ambiguous mapping method but there is a more specific mapping

2 participants