Improvements for Mapster Tool

[DocSvartz]

Improvements for generating mappers from interface :

1. Added support mappers that use internal methods or properties.
2. Added support for marking generated mapper attributes [MapsterToolGeneratedMapper]
   new Mapster.Tool command mapper option:
   • -h: true - Create a mapper with helpers attributes
   • -H: - add additional namespace for generated helpers attributes

Note

By default helpers attributes generate in namespace Mapster.Generated.Attributes.{Filename of assembly} specified in the -a option.
-H: "MyNameSpace" - create next namespace Mapster.Generated.Attributes.MyNameSpace
If assembly filename or the string passed as a parameter -H is not a valid C# namespace, a additional namespace will be created automatically.

[DocSvartz]

@andrerav
That is, if you emulate a cases that is not currently supported:

 public interface IMyTypeMapper
{
internal AddressDTO Map(Address p1);
internal Expression<Func<AddressDTO, Address>> Projection { get; }
}

or

internal interface IMyTypeMapper
{
internal AddressDTO Map(Address p1);
internal Expression<Func<AddressDTO, Address>> Projection { get; }
}

emulation step

1. replace Address to internal

internal class Address

2. in TypeDefinitions set

IsInternal = false,

we get valid mapper :

public partial class CustomerMapper : IMyTypeMapper {
internal AddressDTO Map(Address p1)
{
return p1 == null ? null : new AddressDTO()
{
Id = p1.Id,
City = p1.City,
Country = p1.Country
};
}
AddressDTO TemplateTest.IMyTypeMapper.Map(Address p1)
{
return p1 == null ? null : new AddressDTO()
{
Id = p1.Id,
City = p1.City,
Country = p1.Country
};
}
internal Expression<Func<AddressDTO, Address>> Projection => p2 => new Address()
{
Id = p2.Id,
City = p2.City,
Country = p2.Country
};
Expression<Func<AddressDTO, Address>> TemplateTest.IMyTypeMapper.Projection => p2 => new Address()
{
Id = p2.Id,
City = p2.City,
Country = p2.Country
};
}

I thought this shouldn't work, but the assembly with this class compiles and the mapper itself works when cast to the interface.🤔

[DocSvartz]

@andrerav If I'm not mistaken in the current implementation😃

Now mapper members are created correctly depending on the public/internal access modifiers specified for it or using for maping internal clases.

And IsInternal continues to work as before, forcing the creation of an internal mapper with an internal members.

[andrerav]

@DocSvartz Your approach is more general and solves both #399 and more. I closed my own PR, which had issues as you pointed out.

[DocSvartz]

@andrerav Perhaps it's worth adding [MapsterToolGeneratedMapper] to Mapster.Core instead of generating it for each dotnet mapster mapper call?

Due to the use of the [Mapper] attribute on the interface, it is required to use at least Mapster.Core.

[DocSvartz]

@andrerav Perhaps it's worth adding [MapsterToolGeneratedMapper] to Mapster.Core instead of generating it for each dotnet mapster mapper call?

Due to the use of the [Mapper] attribute on the interface, it is required to use at least Mapster.Core.

I'm merging this for the pre-release publish. If needed, it can be change in the release.