Releases: loedeman/AutoMapper
Regenerated source map, some new testing and stricter TS linting
Bugfix release (and upgraded NPM packages)
Small bugfix release because of stricter TypeScript compiler settings.
Small non functional fixes because of newer TypeScript compiler version
This release brings no new functionality, the existing JS code only gets compiled by a newer version of the TypeScript compiler. A few non functionals (development dependencies) got updated, most important: TSLint.
Internal refactoring of createMap.for(Source)Member
This minor release (no breaking changes according to covering unit tests) consists of a major overhaul of createMap.forMember and createMap.forSourceMember calls.
This major internal overhaul has become a necessity because the code for createMap.for(Source)Member has been there for ages and has become a bit too hard to maintain (and not necessarily something to still be proud of), while a couple of bugs appeared with advanced nested mapping scenarios. Nested mapping should now be a breeze ;)...
This release includes pull request #20 (thanks @rmalveis) and fixes #18 and #19.
Added typings property to package.json
This is a very small bugfix release, just adding a typings property to the package.json file. Type definition file detection has been added in TypeScript 1.6, although it was never actually added to the package.json file.
Support for nested properties with null source values
This minor release (no breaking changes) fixes #15 - it is now possible to specify nested property mappings while having an empty (null, undefined) source property. For those wondering, v1.7.1 never really made it to full production status, sorry for the gap ;)...
Full UMD/Webpack support
Bugfix: Added ES6 support (thanks @vzhidal)
Bugfix: adding new members / return empty object when empty source without mapping
This bugfix release fixes issue #11. It appeared to be impossible to add new members to a destination. Also, the question was to return the source object when it is null/undefined and no mapping has been performed at all, instead of returning an empty object ({}) in that situation.
Bugfix: using mapping profiles does now function as expected
This release is a bugfix release. This release fixes issue #8: when using a mapping profile without also specifying properties outside mapping profile, mapping did not work as expected (thanks, dgroh ;)).