Adapt changes from original fnogatz/xsd2json #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Alban,
thanks for putting such an effort in making xsd2json better! In order to keep getting updates from the original module I've done some little changes on your fork:
xs:includeandxs:importit is necessary to prefix all constraints by its filenameINameNow your version of the Prolog library is nearly the same as mine in fnogatz/xsd2json@084a437. Your given
npm testis still valid.Because the bug of using
type: 'mySelfDefinedType'instead oftype: { $ref: '#/definitions/mySelfDefinedType' }has been fixed in the newest version of xsd2json I will try to remove the fixes in json-processing.js. We should also try to adapt the yet implementedxs:includeandxs:importsupport.