Skip to content
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

draft-07 support #400

Closed
gaoxinyang opened this issue Apr 18, 2018 · 8 comments
Closed

draft-07 support #400

gaoxinyang opened this issue Apr 18, 2018 · 8 comments
Labels
Enhancement Some new desired functionality

Comments

@gaoxinyang
Copy link

In our current project we are using JSON draft-07 schema, is there any plan to introduce the support to draft-07 ? Thanks.

@handrews
Copy link

See #337 as it will be a much smaller follow-on to draft-06 support. To summarize the discussion there, draft-07 requires all of draft-06 so releasing draft-06 as soon as it is ready doesn't really slow down progress to draft-07.

@Julian
Copy link
Member

Julian commented Apr 20, 2018

Yeah think Draft 7 support will hit fairly quickly after that one finally gets merged.

@wolfthefallen
Copy link

Would love the ability to do version 7!

@mgab
Copy link

mgab commented Jul 18, 2018

Is it possible to follow progress or/and pending tasks for any of the two versions anywhere? I'm thinking of a wiki page with TODOs, a label or milestone for pending issues or anything like that.

This would allow people to know not only how far or close new versions are, but also where hands are needed.

@Julian
Copy link
Member

Julian commented Jul 18, 2018

There's a checklist on the draft 6 ticket. On this one, there's a branch (draft7) with support for draft7 on it, and probably will have a checklist as soon as draft6 is fully done.

@Julian Julian added the Enhancement Some new desired functionality label Aug 13, 2018
@iddan
Copy link

iddan commented Sep 23, 2018

Is there a checklist?

@Julian
Copy link
Member

Julian commented Sep 29, 2018

Hi! Beyond the one from the Draft6 ticket, essentially for Draft7 all that's left specifically for Draft7 is adding support for if/then/else, which should be fairly straightforward.

The branch that's out there passes everything else besides those.

  • Draft6 Checklist
  • If/Then/Else
  • New formats
  • Review the changelog, compare with what was added

@Julian
Copy link
Member

Julian commented Jan 17, 2019

The draft 7 specific pieces here are done and merged, so I'm going to close this one at least -- the next stable release will have full draft 7 support other than a format or two that doesn't have an existing implementation.

@Julian Julian closed this as completed Jan 17, 2019
Julian added a commit that referenced this issue Jun 20, 2020
fc05651cc Merge pull request #409 from Stranger6667/dd/add-jsonschema-rs
5f1575a93 Add Rust `jsonschema` crate
2bf95beec Merge pull request #407 from fisxoj/master
9ae956b21 Add common lisp implementation to the list
d4ffd569b Merge pull request #401 from json-schema-org/ether/format-uuid
2d6c45711 tests for the "uuid" format
08f6cdaff Merge pull request #400 from json-schema-org/ether/more-format-ipv6
d3064eb3a some more tests for the "ipv6" format
1f34d3321 Merge pull request #399 from json-schema-org/ether/more-format-idn-email
22adda78c also test the "email" inputs against "idn-email"
25598a3b4 Merge pull request #392 from rjmill/rjmill/test-prop-named-ref-containing-a-ref
8dfa8adc9 Merge pull request #380 from ChALkeR/fix-ecmascript-regex
d595dbf9d backport $ref cases, changing "$defs" to "definitions"
ca8319c9e Fix \W test description
452b5f8f4 Test property named $ref, containing an actual $ref
a01ae5404 Fix ECMA 262 regex whitespace tests.

git-subtree-dir: json
git-subtree-split: fc05651cce3889975f8dbcca38c203d6a396694b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Some new desired functionality
Projects
None yet
Development

No branches or pull requests

6 participants