RegisterCustom should come before ComplexMapCondition

fluentsprings / ExpressMapper

Mapping .Net types

http://www.expressmapper.org

Other

310 stars 65 forks source link

RegisterCustom should come before ComplexMapCondition #118

Open high1 opened 8 years ago

high1 commented 8 years ago

RegisterCustom was used only if ComplexMapCondition was true, it should always be used regardless of the map condition complexity, so it was moved before
removed checkNullExp - registration should take care of the null values itself

high1 commented 8 years ago

This should solve issues with RegisterCustom - it was not always used, and not it will be. I removed checkNullExp, because I think that if a user does register a custom mapping, it should take care of possible null values.