Beanmapper v2.4.1 Release Notes

Release Date: 2018-06-19 // almost 6 years ago
  • 🛠 Fixed

    • Issue #109, Specify the return type for AbstractBeanConverter.doConvert; on extending AbstractBeanConverter, it is beneficial for the developer to immediately see the expected return type for the doConvert method.
    • Bug #111, BeanCollection null list overrides the existing list; when a source and target have been assigned to a collection handler, it will now treat a null value for the source as special, subscribing it to the BeanCollectionUsage rules (default: CLEAR). That is, it will REUSE the target, CLEAR it, or CONSTRUCT a new one. This is the most logical behaviour with Hibernate on the other side.
    • 🏗 Bug #112, Strict mapping messes up the build sequence; The validation took place before all configuration was done, resulting in collection handlers not being available in some cases. The validation of strict classes is done as part of the last step of the BeanMapperBuilder.build() method, after all required steps have been taken.