You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use it to not have null values copied from the source object to the destination object. In these cases the source object already exists and I am copying values over to the destination object. It looks like in changeset f5daca4 a change was made to call propertyMap.ShouldAssignValue sooner. Previously the call to ShouldAssignValue looked like this:
This was something that worked in Automapper 2.0 that now appears to be broken in Automapper 2.1.
I have the following statement:
I use it to not have null values copied from the source object to the destination object. In these cases the source object already exists and I am copying values over to the destination object. It looks like in changeset f5daca4 a change was made to call propertyMap.ShouldAssignValue sooner. Previously the call to ShouldAssignValue looked like this:
but now it looks like:
I can work around this by calling the following:
but this seems to be working around something that should just work.
The text was updated successfully, but these errors were encountered: