Found one bug in Dapper.Contrib (1.50.0.0) while inserting an entity with long id value

In class Dapper.Contrib.Extensions.SqlMapperExtensions we found one bug as below -

Starting from line number 47 -

int num;
    if (!flag)
    {
        num = **formatter.Insert(**connection, transaction, commandTimeout, tableName, stringBuilder.ToString(), stringBuilder2.ToString(), list, entityToInsert);
    }
    else
    {
        string text = string.Format("insert into {0} ({1}) values ({2})", tableName, stringBuilder, stringBuilder2);
        num = SqlMapper.Execute(connection, text, entityToInsert, transaction, commandTimeout, null);
    }
    if (expr_121)
    {
        connection.Close();
    }
    return (long)num;

formatter.Insert is returning long but getting stored in int variable. This is a bug and must be fixed soon.

In Dapper.Contrib.Extensions.SqlMapperExtensions, start around line 47 and inspect the formatter.Insert result and its local variable. Confirm the insertion path preserves a long ID value and check the surrounding insert behavior; done means entities with long IDs insert without truncation or overflow.