- You have now 2 solutions to expose properies :
- with @Expose decorator of class-transformer
- Come back of getters / setters (from v1.0.1). If you define a getter or a setter for a property, it will be exposed.
- Prettier
- Controls on MappingOptions
- Installation
- The @Mappings decorator doesn't work without @Mapper on the parent class
- The ability to force the type of a targeted property
- The ability to target a targeted property in depth
- Implicit Mapping for more than one parameter
- Reinforcement of the tests
- Before the script auto-generated by @Mappings did heavy calculations, like selecting the right @BeforeMapping or @AfterMapping methods before executing them. So when a method was called, the computation time varied depending on the amount of methods inside the mapper.
Now, all the selection calculations are done when the mapper is instantiated, and the auto-generated mapping method does the minimum. - Adding of one provided mapping method: getOrEmptyString
- Review of returned exceptions
- The getConcatProperies without a seprator doesn't work well, so now the separtor must be filled in.
NOTE: This version is deprecated.
- more scalable code with linter and jest tests
- getConcatProperties couldn't be used
- parameters with underscors are now recognized
NOTE: This version is deprecated.
- The getters / setters have no more influence to map an object. It is now necessary to expose each attribute.
- @BeforeMapping: perform some actions before the mapping process
- @AfterMapping: perform some actions after the mapping process
- @MappingTarget: provide the mapping object throw mapping methods changes in thrown exceptions
- the getters/setters are no longer required in object's classes for mapping