Mapping fails when a record property is Ignored

[amantinband]

The following will throw an exception:

public record User(string Name);

public record UserDto(string Name);

TypeAdapterConfig<User, UserDto>.NewConfig()
    .Ignore(dest => dest.Name);

var user = new User("Amichai");
var userDto = user.Adapt<UserDto>(); // <-- throws Mapster.CompileException: Error while compiling, with inner exception: System.ArgumentException: Incorrect number of arguments for constructor

Is this by design? Didn't see this documented

[skuirrels]

This needs to be solved. It precludes the use of Mapster.

[stagep]

In order to identify issues that are still active, we are closing issues that we believe are either resolved or are dormant. If your issue is still active then please reopen. Thanks.

[DocSvartz]

@amantinband @andrerav Yes, it not supported in origin design.

I hope add this :)

But for the current example this doesn't make sense. instance of UserDto in this case it cannot be created.

I don't think your goal is to always get null or String.Empty in this property ?

[DocSvartz]

linked #707
@andrerav ignoring works too well :)
To create a construct, data about the presence of such a variable is not received at all.
fix is almost complete :)

[DocSvartz]

linked #723

[DocSvartz]

linked #458