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
Yes it probably should. Because you can easily end up loading files that do not specify data types for child objects, if the code finds a unknown data type and parent!=null it will always use the parent data type. So nothing bad is currently happening.
However we really should try to get the datatypes correct at the UI level and the protection against null child items should be at the import level. If i cleaned up this it would remove a fair chunk of code that is only there to deal with bad situations such as UNKNOWN datatypes ;-)
I'm currently between PCs so may take a day or two before i can get any coding done
I'm talking about this line.
Should this not be the datatype of the parent? Also inheriting accessType and PDOtype would be handy.
I'm not sure about this, so no pull request yet ;-)
The text was updated successfully, but these errors were encountered: