Repository navigation
Automapper keeps closing the issues related to Nullable source to Non-Nullable destination mapping #4627
Description
Activity
All the previous issues are before the commercial fork (which we've kept for posterity). The previous versions were provided as-is, with no support. Now that commercial backing and support exists, we can revisit these issues.
Just as an aside, we're going through ALL the older "closed won't fix" issues to prioritize fixes for common issues, like this one.
We'll take a look!
Took a look. There are two things tangled together here:
dest.Int = src.NullableInt ?? default(int)with no condition is inherent — a name match always produces an assignment and a non-nullable destination member has no way to represent absence. Not fixable, but it was undocumented.- The
Conditionsource member argument was a real bug. It is documented as the source member, but we passed the value after conversion to the destination member type, so null had already collapsed todefault(T)before your condition ran. That is what made the PATCH scenario unexpressible.
#4655 fixes (2) and documents (1). Reopened #2918, #2999, #3926 and #4530 to track.
Reacted by MarioVolarevic
This is a problem which has been present from 2018 and still hasn't been solved, which is very useful for the PATCH scenarios.
I won't write steps to reproduce because you can see them in the linked issues:
#2918
#2999
#3926
#4530
Amd you keep closing all similar issues, when there is obviously a need to support this behaviour.
It's even missing in the documentation so it has to be discovered each time by a new individual.