You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Type as PropertyPart CustomType instead of only name (#347)
* Don't use only name for PropertyPart.CustomType
- Use the constructor of TypeReference with Type argument instead of the
constructor with string argument in the overloads of CustomType in
PropertyPart where an explicit Type is passed.
- This fixes the problem that Fluent NHibernate may map a wrong type
for a property although an explicit type was passed to CustomType.
This problem can happen if there are two types with names which only
differ in upper / lower case. Such similar type names can e.g. be
caused by obfuscation tools.
* Adapt tests to new behaviour of PropertyPart
- The production code of the CustomType overloads of PropertyPart was
changed to use a different constructor of TypeReference when an
explicit Type was given. This caused two tests to fail although the
code still should work correctly.
- Change failing tests to expect the new behaviour.
+semver:fix
0 commit comments