-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restriction base not used in generation #738
Comments
Usually the base classes are not flattened unless, there is a reason, I am gonna take a look and see what's the issue with these restriction bases |
Early on, xsdata couldn't handle type overrides very good, so whenever a subclass was overriding a parent class field and the types didn't match the base classes were flattened. That part of the code is no longer relevant and actually had a few major flaws. After I removed the faulty code, a few more issues came up and I had to harden a few things in compound fields. As always the netex schemas keep on giving some excellent use cases 🚀 Thank you @skinkie for the report, the fix is on master, give it a try and let me know what you think. |
@tefra will try! :-) |
The output for netex suite just got a lot smaller |
Let's hope that my mro analyzer still works ;-) |
I am currently using analysis on mro basis in order to figure out how objects relate to eachother.
I notice that "restriction base" is not affecting the schema generation. Below are some examples. Can the restriction base used for inheritance. Or am I missing the point of the restriction in the first place?
NeTEx-CEN/NeTEx#407 (comment)
The text was updated successfully, but these errors were encountered: