-
Notifications
You must be signed in to change notification settings - Fork 26
Draft 6 support #114
Comments
draft-06 is out! |
Hi, just reading this issue through. Does this mean I can validate (pretty simple) Draft 6 schemas with json-guard? PHP support for draft 6 looks non-existent atm and I need draft 6 for the "named enum" work around described here: json-schema-org/json-schema-spec#57 This issue looks promising. Anything I can do to help if this isn't already working out of the box? |
@danballance in the meantime, you can always use a single-element |
Hello,
Not yet. json-reference will mostly work with Draft 6 schemas (it supports
To support draft 6 we need a new rule set (see the docs for more info) and constraints for the changes in Draft 6. Most of the constraints can probably decorate the draft 4 version to add the new logic. The JSON Schema Test Suite will need to be updated to pull in the draft 6 tests (see composer.json) and you can use that to write the new rule set. If you or someone else wants to tackle that let me know and I can answer any questions. I probably won't have time to do this myself anytime soon. I am planning on tackling #122 first since I need it for work. |
@handrews yes that's what we are doing for now. Although I am seeing some other features in draft 6 that we could make use of. @yuloh thanks for clarifying. I am considering trying to take this on as a weekend project, but I'm not free now until January 2018. I really would like to help with this. I'll see what I can organise in my home life and come back to you. |
@yuloh ping Draft 7 is out! |
This is already supported by the dereferencer.
We need a new rule set and constraints.
The text was updated successfully, but these errors were encountered: