Resolves issue #277
This extension allows:
and resolve them:
Added named mappings functionality
What situation are you seeing where you need multiple maps for the same two types? Is it different sets of mapping behavior?
a couple of scenarios i have where named mappings have proven useful are with webapi/REST view models and mapping them to entity models, especially when I am trying to maintain a generic type on both controller & service.
firstly, since REST can PATCH partial objects or POST the full object, and both request models are the same viewmodel as far as the api is concerned, named mappings allow me to differentiate in code which mapping to use - basically ignoring certain properties, or taking the destination value for a "Partial" named mapping.
secondly, REST will accept objects with properties that should not be changed in the entity model for PATCH/PUT (date_created, author_id etc) that i would like to ignore, but I would want to set when creating a new entity with POST. so here i would have a "Create" mapping and "Update" mapping.
maybe string names are not the most elegant, a possible better solution could be behaviour or event driven.
i know there are other ways to solve these problems, but the named mappings is a useful solution.
So you can take care of this using 4.2.0, that introduces removing of the static interface to instance-based. Now you can partition configuration as much as you want.