-
Notifications
You must be signed in to change notification settings - Fork 26
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
ref, complexType in element-tag, documentation in non-leaf-tags #8
Comments
Yes, the aim is to extend xsd2json step by step. Currently I'm working on the integration of The best way to get things fixed is to provide some concrete examples. Feel free to open a pull request containing only some test cases in the |
Current status:
|
@fnogatz I have an <xs:complexType name="DocumentLineType1Choice">
<xs:choice>
<xs:element name="Cd" type="ExternalDocumentLineType1Code"/>
<xs:element name="Prtry" type="Max35Text"/>
</xs:choice>
</xs:complexType> FYI, I was just looking into this tool since we're interested in a JSON Schema for some of the ISO 20022 messages. They are quite big and complex, so you might be interested in them, perhaps as some kind of benchmark (the conversion took several minutes). This is one of the XSD's, the one that I'm currently looking into: |
Hey,
at first I have to say, I like your work. It is a great tool that helps me a lot at the moment. In addition I wanted to ask, if you plan further development? There are several things to do I guess.
Of course I saw, you did not commit anything about two months now, but maybe you continued developing at home?
e.g. what about:
These are several things that do not work atm, afaik, and I wanted to ask, if you are going to fix these things, maybe?
Thanks for your answer and have a nice week!
The text was updated successfully, but these errors were encountered: