Support for OpenAPI 3.1

[Former user]

OpenAPI 3.1 landed a few weeks ago, almost four years since the creation of the OpenAPI initiative and their 3.0 release. Here's a blog post with What's New, including webhook support, the ability to refine $refs, and well-formed fragments.

It's obviously hot off the press, but it does add support for some really nice and long overdue features, like having sibling description and default elements with a $ref.

I was wondering whether it's a priority to support it, if there's a roadmap to do so, and if so, whether there are chunks of work we can help with so we can accelerate it.

[Emerson Farrugia]

Oops, forgot to log in. is from me.

[James Navin]

Hi Emerson,

Thanks for raising this.

I don’t have a roadmap per se, but if there are important features you’d like to see support for I would suggest:

1. Raise an issue for the feature (e.g. “Add support for OpenAPI 3.1 Feature X”)
2. Use the issue voting mechanism to prioritize which features get looked at first and/or identify low hanging fruit that can be implement easily/quickly
3. Optionally raise PRs to implement the features you are particularly interested in.

In the meantime I’ll have a read through the whats new blog - thanks for the link!

Cheers,

James

[Pete Cornish]

Hi folks, thanks very much for the great project.

OAS 3.1 support landed in swagger-parser recently: https://github.com/swagger-api/swagger-parser/issues/1535, so hopefully this enables support here too.