Closed adamskt closed 6 years ago
Oops. Parent
vs EffectiveParent
. Perhaps I should come up with better names for those. EffectiveParent
is arguably more useful most of the time, but I didn't want to change Parent
from what it has always been.
Parent
is the class that the property is declared on. EffectiveParent
is the class that we're trying to look at that may have inherited some properties from a base class. Perhaps I'll change EffectiveParent
to Parent
, and Parent
to DeclaringClass
or DeclaringParent
or something.
Yeah, I think there is an issue open to rename all the props so we don't collide with potential props on the EF entities.
Well, these are just internal properties on PropertyViewModel
. When I refactored some stuff this weekend I used one when I should have used the other.
This is broken in 4fc35f4216509324e25e2d468a60219c5598d3e0 In prior versions several entities could share a base class with a foreign key property and related navigation property decorated with the
[ForeignKey(nameof(fkey_property))]
and code generation would proceed as normal. In versions after 2.0.0-alpha-270, errors like the following are displayed and code generation fails:Customer
,CustomerContact
,ElectricMeterExchange
all inherit fromWorkOrderBase
that has these properties: