Consolidate ResolveUsing to MapFrom

[jbogard]

Per #2795 discussion

[lbargaoanu]

A small thing, but I wouldn't mind seeing UseValue gone :)

[jbogard]

Ha, oh right! Because we used to force people to only use MapFrom from properties.

I'd be OK with that,

[lbargaoanu]

OK, it should be simple to do. I'll open a PR whenever :)

[jbogard]

Too late lol

…

On Thu, Sep 27, 2018 at 7:46 AM Lucian Bargaoanu ***@***.***> wrote: OK, it should be simple to do. I'll open a PR whenever :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2809 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGYMoWSY1zeU3ILcuMa9MOZnYaMPkR7ks5ufMizgaJpZM4W7fHD> .

[lbargaoanu]

Nice :)

[yhnavein]

Ok, fantastic. I have replaced ResolveUsing with the MapFrom, but how should I deal nicely with the An expression tree lambda may not contain a null propagating operator error?
That was the whole purpose of using ResolveUsing for me, as it was short and dandy. And I have plenty of null checking in my mappings.

- .ForMember(dest => dest.UserId, opts => opts.ResolveUsing(src => src.User?.Id))+ .ForMember(dest => dest.UserId, opts => opts.MapFrom(src => src.User?.Id))

I find the following solution unacceptable:

.ForMember(dest =>dest.UserId, opts =>opts.MapFrom(src =>src.User==null?(long?)null:src.User.Id))

Is there any other way to deal with this breaking change?

[lbargaoanu]

Check the upgrade guide.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.