#3708 Support CollectionMappingStrategy on @BeanMapping and @Mapping
#3935
+252
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR Support for
CollectionMappingStrategyon the@BeanMappingand@Mapping. This allows for more granular control over the collection mapping strategy at the individual method or property level, rather than relying solely on the global configuration set for the entire mapper.Key Changes
@BeanMappingSupport:collectionMappingStrategyhas been added to the@BeanMappingannotation interface.@Mappingannotation.@MappingSupport:@Mappingannotation interface.@Mapping.With these changes, we can now flexibly control the strategy for populating target collections for specific use cases, without altering the global mapper configuration.
The resolution priority is as follows:
@Mapping>@BeanMapping>@Mapper>@MapperConfig.