-
Notifications
You must be signed in to change notification settings - Fork 168
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
validate.js is unable to validate core schema #17
Comments
Note: this is using my patch for required vs. optional; without that, there are lots more errors about missing required properties ;-) |
What is your patch - you just switch that one line? |
Hmm, seems I accidentally deleted my fork, which has deleted the pull request too. I'll see if I still have a working copy that I can push back up. |
OK, resubmitted the commit that the test case above assumes. Sorry about that. |
I added vows tests on my fork, showing this problem; see laurie71@0a52e1e The tests are run with 'vows test/*.js' |
i think i just came across this same problem. the draft-03 schema restricts a my current workaround is to delete the |
validating the core schema [validate(schema)] causes validate to choke on the '$schema' instance property; [validate(schema,schema)], which should be equivalent, adds an extra 'null' entry to the result. Deleting the $schema property before validating results in a single 'null' in result.errors.
Here's my test script reproducing the problem:
and here's the result of running it:
The text was updated successfully, but these errors were encountered: