If your model has an unsupported property type on it (e.g. an enum or another class) then you should be able to mark this property as being ignored (it can then still be used by your application). However, due to the way the EntityTypeMap auto-maps its properties on construction it doesn't know that the property is to be ignored (this is only found out after construction).
I'm guessing this is quite a sizable change but am thinking the best way would be to separate evaluation an building of the entity mapping from that of the mapping config itself, i.e the mapping config just becomes dumb and something else evaluates this.
If your model has an unsupported property type on it (e.g. an enum or another class) then you should be able to mark this property as being ignored (it can then still be used by your application). However, due to the way the EntityTypeMap auto-maps its properties on construction it doesn't know that the property is to be ignored (this is only found out after construction).
I'm guessing this is quite a sizable change but am thinking the best way would be to separate evaluation an building of the entity mapping from that of the mapping config itself, i.e the mapping config just becomes dumb and something else evaluates this.