CODEWITHSUNDEEP
automapperautomapper-4automapper-10
jmoreno
jmoreno

Reputation: 13561

Upgrading Automapper and mapping zero to null based based on an attribute

I'm not very familiar with AutoMapper but am trying to update AutoMapper 4 to AutoMapper 10 (last version to support .Net Framework) on a project, and I have run into a problem: The ResolutionContext changed in the 4-5 upgrade so that it no longer has a Parent property.

The existing code works with an attribute that is put on properties in the view model where zero is supposed to be treated as a null, and the existing type converter has this code in it:

var prop = context.Parent.Parent.DestinationType.GetProperty(context.MemberName);
var attributes = prop.GetCustomAttributes(false);
var zeroAttr = attributes.Where(a => a.GetType() == typeof(ZAttribute)).ToList();

But as of AutoMapper 5, ResolutionContext.Parent and ResolutionContext.Member no longer exists.

This allows mapping zero to null for any/all view model, as long as the property has the attribute, there doesn't need to a specific mapping for that type (I think that is how it works). If the attribute isn’t on the property the normal mapping is done (zero stays zero).

How can this be done with AutoMapper 10?

I'm thinking it might be some type of ValueResolver...

Upvotes: 3

Views: 135

Answers (0)

Related Questions