ideas about supporting openapi 3.1?

[noahehall]

is that on the roadmap?

if so: how do we follow/support the work being done?

[supertong]

Hey @noahehall , nope, we don't have any roadmaps. Do you have any particular feature that you want the most?

[crizo23]

Just checking in on this feature. OAS 3.1.x has been around a while now and is much better aligned with json-schema. A quote from here

OpenAPI Schema is now valid JSON Schema
Everything inside the schema keyword in OpenAPI is defined by the Schema Object. This has always been loosely based on JSON Schema, and referred to as a “subset superset” because it adds some things, and removes some other things from JSON Schema. This has caused confusion for some folks in the OpenAPI community. To resolve the subset superset problem, contributors from both communities came together, and got these two specifications aligned.

One of the first blockers is oas-validator: Mermade/oas-kit#529.
It says it's "in progress" so that's hopeful.

Recently, koa-oas3 and oas3-chow-chow were updated to major versions which brough in AJV8. Both OAS 3.1.x and AJV 8 support the most recent json-schema 2020 draft. koa-oas3/oas3-chow-chow supporting oas 3.1.x would be nice and bring everything in alignment, not to mention the new stuff and cleanup in json schema draft 2020.

Anyway, I don't have the time/skills to take this on, but it sure would be great!