Private mapper do not work when the parent class implement an interface.

[SebastianStehle]

Describe the bug

I have the basic setup:

internal sealed class UserWithClaims : IUser
{
   private readonly IdentityUser snapshot;

   public UserWithClaims(IdentityUser user, IReadOnlyList<Claim> claims, IReadOnlySet<string> roles)
   {
       // Clone the user so that we capture the previous values, even when the user is updated.
       snapshot = Mapper.IdentityUserToIdentityUser(user);
   }

   [Mapper(UseDeepCloning = true)]
   private static partial class Mapper
   {
       public static partial IdentityUser IdentityUserToIdentityUser(IdentityUser source);
   }
}

But the generated code does not add the namespace to the IUser interface, which is defined in another namespace. So the follow code is generated:

#nullable enable
namespace Notifo.Identity
{
    internal sealed class UserWithClaims : IUser
    {
        private static partial class Mapper
        {
            public static partial global::Microsoft.AspNetCore.Identity.IdentityUser IdentityUserToIdentityUser(global::Microsoft.AspNetCore.Identity.IdentityUser source)
            {
                var target = new global::Microsoft.AspNetCore.Identity.IdentityUser();
                target.Id = source.Id;
                ...
                return target;
            }
        }
    }
}

Expected behavior
The implementing or base classes do not need to be copied to the generated code. if you want to copy that, add the namespaces.

Environment (please complete the following information):

• Mapperly Version: 2.8.0
• .NET Version: 7.0

Additional context
Add any other context about the problem here.

[SebastianStehle]

Sorry, I just realized that private mappers do not work anyway.

[TimothyMakkison]

Hey, thanks for the bug report. I think I can fix this issue

Sorry, I just realized that private mappers do not work anyway.

Private mappers should be supported, just make the containing class partial.
You didn't mean something like #599 did you?

[TimothyMakkison]

This bug has been fixed in 2.9.0-next.4

See #548 for details.

[latonz]

@SebastianStehle can you reproduce your issue with 2.9.0-next.4?