xsdata icon indicating copy to clipboard operation
xsdata copied to clipboard

Naive XML & JSON Bindings for python

Results 88 xsdata issues
Sort by recently updated
recently updated
newest added

I understand the desire to minimize "unnecessary" class types, but in some cases, there is reason to create all SimpleType classes from an XSD. For example, if classes are created...

Schema source: [`https://gitlab.com/crossref/schema`](https://gitlab.com/crossref/schema) (checked out locally at `other_schema/crossref`). There are a couple of different schemas in the repo that I'm looking at, but anything that includes the [`mathml3.xsd`](https://gitlab.com/crossref/schema/-/tree/master/schemas/standard-modules/mathml3) fails to...

Using the compound fields option, the following XML: ```xml ``` generates ```python @dataclass class DeemedRateType2Choice: cd: Optional[DeemedRateType1Code] = field( default=None, metadata={ "name": "Cd", "type": "Element", "namespace": "urn:iso:std:iso:20022:tech:xsd:seev.036.002.09", } ) prtry:...

enhancement

I have 2 things that I need to improve to simplify the generated classes from my xsd file. A sample to illustrate the issue: ``` ``` Child1 is the ideal...

The default generator has to remain compatible with all python versions, but someone could use https://github.com/asottile/pyupgrade to upgrade to 3.10 syntax. ```python Foo | Bar instead of typing.Union[Foo, Bar] FooBar...

Since JSON to xsData is already possible heuristically, would jsonschema be something that would be in scope to directly parse?

enhancement

Currently the code generation is able to add meta data at this level; ```python @dataclass class StopPlaceRef(StopPlaceRefStructure): """ Reference to a STOP PLACE. """ class Meta: namespace = "http://www.netex.org.uk/netex" ```...

Let's add proper model validations...

Current converter warnings only include the token and the types it is being matched to. This makes it hard to narrow down what exactly they refer to without stepping up...

Currently we generate compound fields only when it's absolutely necessary in order to maintain elements ordering between roundtrips. It would be nice to have an option to always group together...

wip