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
Hi! I'm successfully using this great library to generate code from some BIM related XSD files, namely BCF XML and IDS XML specifications.
I've stumbled upon a problem with the latter: XML files created using the generated classes are invalid, because the xs:enumeration and xs:pattern elements have a fixed="false" attribute that is not allowed.
To generate the classes, I used the command
xsdata generate -p ids.model -ds Google --kw-only --slots ./ids.xsd
At the beginning of the file there are some namespace imports:
I can fix this by manually editing the NoFixedFaced without inheriting form Facet, but is there a way to tell xsdata to handle the prohibited use of the fixed attribute (so that I don't have to worry about schema updates in the future)?
The text was updated successfully, but these errors were encountered:
Hi! I'm successfully using this great library to generate code from some BIM related XSD files, namely BCF XML and IDS XML specifications.
I've stumbled upon a problem with the latter: XML files created using the generated classes are invalid, because the
xs:enumeration
andxs:pattern
elements have afixed="false"
attribute that is not allowed.To generate the classes, I used the command
At the beginning of the file there are some namespace imports:
So xsdata generates the three modules:
ids.xml
.xmlschema.py
andxml.py
.The
enumeration
element hasnoFixedFacet
typeand is translated as
noFixedFaced
is based onfacet
, but prohibits the use of thefixed
attribute defined in thefacet
:But this results in an empty
NoFixedFacet
dataclass that inherits from theFacet
class, and it doesn't remove thefixed
attibute:I can fix this by manually editing the
NoFixedFaced
without inheriting formFacet
, but is there a way to tell xsdata to handle theprohibited
use of thefixed
attribute (so that I don't have to worry about schema updates in the future)?The text was updated successfully, but these errors were encountered: