Open FaustoNascimento opened 9 months ago
I've also tried it with DryIoC with the following registration:
var container = new Container();
container.Register<BDestination>();
TypeAdapterConfig<Source, BDestination>.NewConfig().ConstructUsing(_ => container.Resolve<BDestination>(IfUnresolved.Throw));
var source = new Source();
source.Adapt<BDestination>();
But this also fails with the same error - although I swear I had it working with DryIoC before...
Ok cause I was really certain that this worked before with DryIoC and the only other thing I could think of was that I updated Mapster... I decided to go back to 7.3.0 and that works so this looks a regression bug?
I found some pretty weird behaviour with Mapster 7.4.0...
Imagine you have the following DTOs:
With no configuration at all, Mapster should be able to map between these two types and it can... but only depending on how it's invoked:
To make things worse ... if your DTOs are not as simple as this example and you use DI/IoC and you combine this with
TypeAdapterConfig<Source, BDestination>.NewConfig().ConstructUsing()
then the results are again unexpected depending on the Expression passed:Any ideas what's going on and any potential workarounds?