-
Notifications
You must be signed in to change notification settings - Fork 113
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
Consider using the official test suite? #102
Comments
(not the maintainer) As far as i know the module isn't in full compliance with the test suite yet. This issue seems to be the most prominent which would fail many tests of the official test suite. |
Can you point me to the official test suite? |
Note that we use Backlog for all open issues, even if there are no plans to work on it. Issues worked on are marked with a milestone. |
Note that we use Backlog for all open issues, even if there are no plans to work on it. Issues worked on are marked with a Milstone. |
You can find it here: https://github.com/json-schema-org/JSON-Schema-Test-Suite |
Hello!
Given the importance of this module when using JSON Schema, I wonder, why not use the official test suite?
I did read you don't want external dependencies. Currently we do not offer a maintained version of the test suite as an npm release. We usually suggest people use git submodules to capture the tests they need.
I do see you have tests beyond validation. The official test suite currently only covers validation.
If it's difficult to justify time to do this, I may be able to help you find some additional justification.
Making the change is beyond the time I can offer currently.
The text was updated successfully, but these errors were encountered: