Currently, when we create an update mapping such as:
User updateUserFromDto(@MappingTarget User user, UserDto userDto);

In order to have null checks, we must configure the Mapper annotation (in the class level) to have nullValueCheckStrategy = NullValueCheckStrategy.ALWAYS.

But this generates null checks everywhere, including the creator mappers.
It would be awesome if there was a property in @mapping like "nullCheck=true/false", so that we can fully control that.