ReverseMap with AsProxy

[korser1]

What do you think about making AsProxy method returning TMappingExpression, and then support ReverseMap?

Example

class Srource {
   public int Value { get; set; }
}

interface IDestination {
   int Value { get; set; }
}


CreateMap<Source, IDestination>().AsProxy().ReverseMap();

[lbargaoanu]

I guess it could work. A PR is welcome. Probably I thought it should stand out as the last in the chain.
That would be a binary breaking change, so it implies a major version bump cc @jbogard.

[korser1]

So would this be a breaking change then?

Imagine that someone uses AsProxy now. They cannot chain anything after AsProxy call. And we are not breaking anything for them.

The implementation of the method will not be changed.
But fluent syntax will work for interfaces as for classes.

classes:
CreateMap<Class1, Class2>().ForMember(...).ReverseMap().ForMember(...)

interfaces:
CreateMap<Interface1, Interface2>().ForMember(...).AsProxy().ReverseMap().ForMember(...).AsProxy()

Before version 11 we didn't use AsProxy as it was automatically in effect.

[jbogard]

It's a binary breaking change in that it's not a drop-in replacement. You'd have to re-compile

[korser1]

Sure

[lbargaoanu]

@korser1 https://docs.microsoft.com/en-us/dotnet/core/compatibility/categories
You're talking about source compatibility, but we have to maintain binary compatibility for the same the major version.

[korser1]

@korser1 https://docs.microsoft.com/en-us/dotnet/core/compatibility/categories You're talking about source compatibility, but we have to maintain binary compatibility for the same the major version.

Yes, understood. So would you like to have this capability in the next version? I played a little bit, looks good. Will prepare PR.