mapstruct-plus/docs/en

home, modules, bannerBrand, isShowTitleInHome, actionText, actionLink, features, fotter

home	modules	bannerBrand	isShowTitleInHome	actionText	actionLink	features	fotter
true	BannerBrand Features MdContent Footer	bgImage title description tagline buttons socialLinks /bg.svg MapStructPlus Probably the simplest and most powerful Java Bean transformation tool MapStructPlus is an enhancement tool of MapStruct. On the basis of MapStruct, it realizes the function of automatically generating Mapper interface, and strengthens some functions, making Java type conversion more convenient and elegant. text link Quick Start /en/introduction/quick-start.html text link type FAQ /en/guide/faq.html plain icon link LogoGithub https://github.com/vuepress-reco/vuepress-theme-reco	true	About	/views/other/about	title icon details Quick launch The conversion between Java classes requires only additional annotation, reducing the tedious and error-prone development task title icon details Efficiency light Based on the annotation processors, all of the generation is done at compile time title icon details Conversion change Property conversions are based on getter/setter methods in the class title icon details Compatibility any Support JDK8~17、SpringBoot2~3 title icon details Multi-class conversion structure Support for a single class to configure multiple type conversions title icon details Conversion between Map and Object type More powerful map-to-object functionality	startYear 2023

Other Open Source Project

• EasyRelation：GitHub | Gitee | Document

Latest Version

• maven

<dependency>
    <groupId>io.github.linpeilie</groupId>
    <artifactId>mapstruct-plus-spring-boot-starter</artifactId>
    <version>1.4.0</version>
</dependency>

• gradle

implementation group: 'io.github.linpeilie', name: 'mapstruct-plus-spring-boot-starter', version: '1.4.0'

Change Log

1.4.2

Sure, here is the translated update document:

---

Updates

• feat: Added the mapperNameSuffix attribute to the AutoMapper annotation. This supports adding a suffix to the generated conversion interface name, and the reverse conversion interface will be effective under the default rules.
• feat: Adapted the Mapper annotation to support the following attributes: unmappedSourcePolicy, unmappedTargetPolicy, typeConversionPolicy, collectionMappingStrategy, nullValueMappingStrategy, nullValueIterableMappingStrategy, nullValuePropertyMappingStrategy, nullValueCheckStrategy, and mappingControl.
• feat: Adapted the Mapping annotation to support the following attributes: constant, qualifiedBy, nullValueCheckStrategy, nullValuePropertyMappingStrategy, and mappingControl.
• feat: Adapted MapStruct configuration to support the following attributes: typeConversionPolicy, collectionMappingStrategy, nullValueIterableMappingStrategy, nullValueMapMappingStrategy, nullValueCheckStrategy, mappingControl, unexpectedValueMappingException, and suppressTimestampInGenerated.
• fix: Resolved the issue of class name conflicts generated in different packages within the same module.
• feat: Added the reverseConvertGenerate attribute to the AutoMapping annotation to control whether to generate reverse conversion logic, adapting to more complex application scenarios.
• fix: Fixed the issue of conversion rule conflicts when both parent and child classes are configured in targetClass.
• fix: Resolved class name conflicts of configuration classes and proxy classes in different modules.
• feat: Added the useEnums attribute to AutoMapper, supporting manual configuration of required enums for conversion, solving the issue of automatic conversion of enums across modules.
• Optimized the logic for generating conversion interfaces.

1.4.0

• Optimize complex object conversion logic, take up less meta-space! and faster!
• Get rid of dependencies such as hutool, which currently only rely on MapStruct in the project.
• The adaptation object loop nesting scenario
• feature#63 AutoMapping、ReverseAutoMapping supports qualifiedByName,conditionQualifiedByName,and dependsOn properties.
• issue#I93Z2Z AutoMappings supports configuration on methods.

Points to note for upgrading 1.4.0

• 1.4.0 and later versions, complex object comparisons reply on ConvertMapperAdapter generated in the project, which may cause NoSuchMethodError exceptions under multiple modules because the Class Loading mechanism will load only one, of course, this problem has been around before, and the odds are probably lower, so be sure to configure the adapterPackage to avoid this problem with multiple modules.
• Map to object conversions still rely on class conversions in hutool, and additional hutool-core dependencies need to be introduced if this functionality is required.

1.3.6

• Compatible with internal class conversion.
• The targetClass in the AutoMapping annotation supports configuring the parent class.
• AutoMapperConfig and AutoMapMapperConfig package and class name generated automatically by the framework support configuration.
• Supports AutoMapping annotations configured in the parent class.

……

Code Warehouse

• Github
• Gitee

Participate and contribute

• Contribution Code: You are welcome to submit an issue or pull requests
• Maintain Documents: Docs directory under the project directory, welcome to participate in the translation and revision

Links

• RuoYi-Vue-Plus
• RuoYi-Cloud-Plus