Skip to content

#2250, #2324 Do not throw error when qualifier is missing on iterable mapping - #2333

Merged
filiphr merged 1 commit into
mapstruct:masterfrom
filiphr:qualified-iterable-mapping
Jan 30, 2021
Merged

filiphr merged 1 commit into
mapstruct:masterfrom
filiphr:qualified-iterable-mapping

Conversation

@filiphr

@filiphr filiphr commented Jan 16, 2021

Copy link
Copy Markdown
Member

With this change we are relaxing the error handling when qualifiers are used in @Mapping
and we allow defining qualifiers for collections / array mapping to mean the same as if it was defined on @IterableMapping
i.e. apply the qualifier on the element mapping

Fixes #2250
Fixes #2324

…issing on iterable mapping

With this change we are relaxing the error handling when qualifiers are used in `@Mapping`
and we allow defining qualifiers for collections / array mapping to mean the same as if it was defined on `@IterableMapping`
i.e. apply the qualifier on the element mapping
@filiphr
filiphr requested a review from sjaakd January 16, 2021 19:03

@sjaakd sjaakd left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@filiphr

filiphr commented Jan 30, 2021

Copy link
Copy Markdown
Member Author

Thanks for the review

@filiphr
filiphr merged commit 0d8bbac into mapstruct:master Jan 30, 2021
@filiphr
filiphr deleted the qualified-iterable-mapping branch January 30, 2021 08:43
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.

Why did you make qualifiedByName more strict with collection mappings in 1.4.1.Final? Cannot map a collection with named mapping method

2 participants