replace original xsd2json with node-xsd2json for PR#5
Closed
albanm wants to merge 62 commits into
Closed
Conversation
Owner
|
Did the first step: I wrote a node wrapper and published the xsd2json module on npm. |
Owner
|
|
…are valid against ISO String
use regex pattern instead
Owner
|
Since both versions diverged too much and my initial pull request to adapt the interface changes into the fork got ignored, I will close here. Thank you for putting time into your fork. I hope, sometime both versions are similar in respect of their features :) |
This file contains hidden or 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
5 participants
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.
Hello,
First of all: I absolutely don't expect you to accept this PR as it is.
It contains a whole new node.js CLI program that wraps around your original prolog program in an attempt to fix the limitations I encountered. You can have a look at the readme for instructions on how to test it.
Most of it you will probably consider dirty workarounds, but I am quite in a hurry to validate the feasibility of XSD->JSON schema for my company. And I need support both for inclusions and type extensions. I will be glad if my code shrinks when your program makes progress.
Of particular interest for you: the test directory contains a small set of XSDs with a good overview of inclusions and extensions test cases.
Thanks