Julian Berman
Julian Berman
[§4.2.2 of the specification](https://json-schema.org/draft/2020-12/json-schema-core.html#name-instance-equality) says, for string equality, that it is defined by: > [...] both are strings, and are the same codepoint-for-codepoint; [...] We should add some tests to...
The draft-next folder contains tests for in-development next versions of the specification. It allows us to get ahead of testing before the spec is complete. At the minute in order...
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...
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/
There should be a mechanism by which implementers (currently mentioned in the README or otherwise) can submit their implementation to be automatically tested and displayed on each commit to the...
This seems to be a point of confusion, or even contention, so we need to document it. The test suite is not a set of what schemas or instances one...
We should have some tests whose `schema` is a meta schema and whose instances are schemas. This would constitute essentially a test suite for the meta schemas, but is also...
This suite is generally not versioned (despite such things having been requested in the past). Regardless though, it is important to define exactly what sorts of backwards compatibility we offer....
Hi! Was wondering what you think about @handrews' [Relative JSON Pointer](https://tools.ietf.org/html/draft-handrews-relative-json-pointer-01) specification. Do you feel it has a place within this library, or would you rather it be separate? (I...