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
When creating a new Feature (and possibly other objects) with the properties = a child class, then the Parent properties aren't in the resulting properties.
Using this code:
// class structurepublicclassParent{publicstringParentString{get;set;}="Test Parent";}publicclassChild:Parent{publicstringChildString{get;set;}="Test Child";}// run this bitvarls=new LineString(newList<Position>{new Position(47,8),new Position(47.1,8)});varx=new Feature(ls,new Child());// <--
results in the following value for x.Properties:
x.Properties
Count = 1
[0]: {[ChildString, Test Child]}
Where I'd expect it to have both ChildString and ParentString properties.
Is this an oversight, or is it maybe configurable somehow?
Otherwise thanks for the great library :)
The text was updated successfully, but these errors were encountered:
Hi @Jadaw1n, thanks for taking time.
The current method reads public properties from the supplied type, and could look at the BaseType.
I'm not sure on how to implement this. @matt-lethargic I would recurse on BaseType until hitting "System.Object". I don't know if there's a better way.
BTW perfs seem awful, maybe should we test and implement a simple property cache to speed up things.
Hi
When creating a new Feature (and possibly other objects) with the properties = a child class, then the Parent properties aren't in the resulting properties.
Using this code:
results in the following value for x.Properties:
Where I'd expect it to have both ChildString and ParentString properties.
Is this an oversight, or is it maybe configurable somehow?
Otherwise thanks for the great library :)
The text was updated successfully, but these errors were encountered: