Look into what sort of work is required to do this.
Maybe everything can stay the same and there is a map type or something that can be changed.
Type = ClassMapTypes.ConstructorParameters;
Map( m => m.Id );
Map( m => m.Name );
Would it be worthwhile to look at how EF Core does it?
https://docs.microsoft.com/en-us/ef/core/modeling/constructors
I like that convention.
When EF Core creates instances of these types, such as for the results of a query, it will first call the default parameterless constructor and then set each property to the value from the database. However, if EF Core finds a parameterized constructor with parameter names and types that match those of mapped properties, then it will instead call the parameterized constructor with values for those properties and will not set each property explicitly.
any update on this, really would be a handy feature?
It's still planned. There are a few things that have higher priority though and I don't have a lot of time at the moment.
I'm having massive issues with this at the moment. It may warrant a separate support ticket.
I have raised a separate ticket #1482
Most helpful comment
I like that convention.