Support for JSON Schema 2019-09

[letmaik]

My own use case would be to validate the schemas in the upcoming Open API 3.1 spec which are based on 2019-09. Historically OpenAPI has used a forked/incompatible variant of JSON Schema but with 3.1 it is a strict superset, meaning that any JSON Schema validator, like valijson, can be used for validating request payloads etc.

[tristanpenman]

I'll take a look at what will be involved. I haven't been following development of the spec, but if it's not too difficult to support it, I'm happy to do so.

[gregsdennis]

Draft 2020-12 is now available (which OpenAPI 3.1 actually depends on, not 2019-09), and we're working on the next one. Do you need help or guidance?

[iamcm1]

Hi @tristanpenman , I have interesting to know is there a plan for Valijson to support latest draft 2020-12 or 2019-09?
Thanks!

[redlars]

@tristanpenman: Any plans to support draft 2020-12?

[tristanpenman]

Hi @redlars - I don't currently have plans to expand to draft 2020-12, at least until some long-standing issues with circular references have been resolved. However, I might be able to prioritise and accelerate implementation of some of the new features if you highlight what it is that need.

[gregsdennis]

@tristanpenman I'm curious what those issues are and how they could hold up supporting 2020-12. If anything, 2020-12 should be easier to support than 2019-09, which you already support.

(Unless it's the burden of trying to manage code you don't care for but aren't yet emotionally ready to tackle, which I completely get.)

[tristanpenman]

Fair question. It's mostly this one that has been bugging me: #200. There are some similar problems that I've been notified of by oss-fuzz.

I had hoped to tackle some refactoring that I believe will address this before attempting to support other drafts of JSON Schema. Perhaps not necessary, strictly speaking. So it may be worth treating them as separate roadmap items.

[redlars]

@tristanpenman: Really appreciate your quick response and the offer to help. We are using $defs and minContains and maxContains but we have a general concern of using a library that does not support a specification that was released almost 4 years ago. Do you have a plan for approximately when you expect full draft 12 compliance? Sorry for begin so negative :-)

[tristanpenman]

Hey @redlars, that's helpful to know what you're using. The spec includes changes that will be non-trivial to implement (i.e. annotations) but there is also some low hanging fruit.

As for timelines, I honestly can't say when complete support for 2020-12 would be available. I've had a look at the major changes in 2019/2020 and made a list that I can tackle over the coming weeks, but anything that requires non-trivial refactoring may take longer.

Keep an eye on this draft PR for progress: #234