Access to already resolved destination properties when using resolve about mapper

[nartc]

The order of the mapping configurations is reversed (due to the reason we talked about on Discord). So if you want to access d.fullName in d.fullTitle, do the following:

createMap(Source, Destination)
   .forMember(d => d.fullTitle, ...)
   .forMember(d => d.fullName, ...)

d.fullName is configured last so it will be mapped first. If you were to use any Member Map that has access to destination object, you would have access to d.fullName.

Another approach is to use afterMap like following:

createMap(Source, Destination)
   .forMember(d => d.fullTitle, ignore()) // we ignore it
   .forMember(d => d.fullName, ...)
   .afterMap((source, destination) => {
      destination.fullTitle = ...; // map it here. At this moment, destination is ensured to have all manual-configured properties mapped.
   })

I'm going to close this issue until there's change in the future. If there is, I'll open a new issue to keep track. Thanks for the issue.