AssertConfigurationIsValid does not fail when mapping from nullable type to non-nullable type

Source/destination types

public class Source
{
    public Guid? OptionalRelationId { get; set; }
}

public class Destination
{
    public Guid OptionalRelationId { get; set; }
}

Mapping configuration

CreateMap<Source, Destination>();

Version: 8.1.0

Expected behavior

Mapper.AssertConfigurationIsValid(); throws an AutoMapperConfigurationException

Actual behavior

The configuration is asserted to be valid.

Steps to reproduce

class Program
{
    static void Main(string[] args)
    {
        Mapper.Initialize(x => x.AddProfile<Mappings>());

        try
        {
            Mapper.AssertConfigurationIsValid(); // Does not throw
        }
        catch (AutoMapperConfigurationException e)
        {
            Console.WriteLine(e);
            throw;
        }
    }
}

[lbargaoanu]

I disagree, I think the actual behavior fits with how AM works, trying to make the mapping work if there is a reasonable default. Most people want to ignore validations, not add new ones 😃 cc @jbogard

[lock[bot]]

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.