update the test suite for draft-next

[hauner]

not all tests align with the draft-next schemas

[gregsdennis]

Can you provide details of misaligned tests that you've found, please? Just saying "it's wrong" isn't particularly helpful.

[hauner]

draft-next/id.json

• "Valid use of empty fragments in location-independent $id"/"Identifier name with absolute URI" is not valid anymore because the ˋ$idˋ pattern changed in core.json

that is the only one I checked 😉 I stopped after you mentioned that the tests are not up to date...

I can check my other failing tests if it helps.

[notEthan]

That test is dropped by #718 (merged just now).
Any other problems?

[hauner]

I'm down to two test failures (unevaluatedProperties/propertyDependencies) implementing draft-next, so I think there is no "wrong" test anymore.

I wonder if there are missing tests though. draft-next talks about

"contains", "minContains", and "maxContains" now apply to objects as well as arrays"

and I expected some failing tests for the object case but there are none.

contains.json has a few changes but I don't see any tests explicitly on objects.

[gregsdennis]

contains applied to objects for a short time, but we decided not to do that.

Honestly, I wouldn't worry about getting draft-next right now. It's not published, and there's clearly work to be done. We're going to have to go through it carefully before publication.

[Julian]

Sounds like we should close this then. If you have specific issues nonetheless (of tests which don't match the spec text), open those please.