-
Notifications
You must be signed in to change notification settings - Fork 11
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
implimentation #10
Comments
Yes, this is not really a full implementation. I implemented only parts of validation needed for my XSD. :-( So there are many cases which it does not handle. But it should not be too hard to add them. |
it would be really nice to contribute some time to it. maybe you can tell me more about the error and the architecture of your "validator.js" file and we can collaborate on making it handle an example like mine in our spare time? |
It would be great if you could make a pull request with a test for this particular failing XSD and XML. |
yeah i'll look at the other test files and see if i can pull something together and do a pull request. |
having a hard time with your implementation. i was previously using xml2js so i know what i can take advantage of from there. but i wanted to take advantage of the xsd somehow and found your module.
Your validator seems to get all the way down to the bottom level of the xml and then throws an error. I think i have the proper xsd for my xml but not sure what the problem is here.
is the structure it i believe is diving into.
Here is the schema.xsd entry i believe corresponds to the data.
further.. the enum looks like this
All this looks correct to me yet your module reports the error...
if necessary i can provide the full xsd and the full sample xml. i'm sure we can work together to make your module better if necessary. This should be a good real world example to go off of.
The text was updated successfully, but these errors were encountered: