JSON-Schema-Test-Suite
JSON-Schema-Test-Suite copied to clipboard
A language agnostic test suite for the JSON Schema specifications
I'm working on updating my validator to consume the latest version of the test suite (after about 18 months; I usually aim for once per year but hey...), and hit...
It used to be that `tox` was a single entry point that ran exactly what Travis ran. ~~We now run some additional things (notably the JS validator), but there still...
Oddly enough, the "local" version worked fine with my implementation, while the "remote" version broke it. This is my first time adding a remote case. I tried to amend the...
More argument combinations for multipleOf, including floats that will be treated as integers, as these might be internally represented as floats rather than ints, and therefore may behave differently. All...
Keywords that are only in effect with instance data of one type should never interfere with keywords that require a different instance type. In particular, implementations should not attempt to...
We should have a test that verifies that `$ref` is not affected by `$recursiveAnchor`
This has come up as a question a few times. `propertyNames` doesn't interact with other keywords. - [ ] `additionalProperties` and `propertyNames` (applies to earlier drafts as well) - [...
E.g. #22 is only optional for languages without a distinction between ints and floats.
See maybe: https://github.com/typicode/husky or https://pre-commit.com/