Non-unform mapping to get-only properties of a target interface

Using Mapster 7,2,0, when mapping to an interface with both readonly and writeable properties results in readonly properties assigned default values. Mapping to an interface with readonly properties only results in readonly properties being populated with values from the source, e.g.

public interface ITarget // GetOnlyProperty will be assigned value from source
{
  int GetOnlyProperty {get;}
}
public interface ITargetWithGetSetProperties // GetOnlyProperty will be 0, GetSetProperty will be assigned value from source
{
  int GetOnlyProperty {get;}
  int GetSetProperty {get;set;}
}

Seems like this behavior was introduced by this commit

In my opinion, properties should be mapped regardless of whether an interface is completely "readonly" or not. Isn't a "readonly" interface simply an edge case of an interface which happens to lack writeable properties?

Merge pull request #375 from andrei-traktatovich/feature/init-readonl…

Navigation Menu

Repository navigation

Non-unform mapping to get-only properties of a target interface #374

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Non-unform mapping to get-only properties of a target interface #374

Description

Activity

andrei-traktatovich commented on Sep 16, 2021

andrei-traktatovich commented on Sep 16, 2021

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions