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

add openapi 3.1 support #5372

Open
wants to merge 11 commits into
base: main
Choose a base branch
from
Open

add openapi 3.1 support #5372

wants to merge 11 commits into from

Conversation

chrisradek
Copy link
Member

This PR adds support for Open API 3.1 in the @typespec/openapi3 package.

The changes in this PR includes:
#4946
#5035
#5245
#5246

chrisradek and others added 10 commits November 6, 2024 09:48
)

This PR adds a new `@typespec/openapi3` emitter option to support
specifying which Open API 3.x specs to output.

Currently marked as `@internal` since currently only 1 version is
actually supported. Once `v3.1` is supported we can remove the
`@internal` annotation.

---------

Co-authored-by: Christopher Radek <[email protected]>
Related to #5009 and #5010

This PR starts the work of getting an Open API 3.1 emitter in the
`@typespec/openapi3` package.

There are a few changes introduced in this PR:
1. Added the `OpenAPIDocument3_1` and related types. The biggest change
here is updating the Open API schema to be based on Json Schema 2020-12.
The Json Schema types don't currently exist in `@typespec/json-schema`
so I added them to `@typespec/openapi3` for now while iterating. Can
move to `@typespec/json-schema` now or later if we want.
2. Created the OpenAPISchemaEmitter3_1 class to target Open API 3.1
schemas. Currently completely standalone from Json Schema and Open API
3.0 schema emitters.
3. Updated nearly all tests to now run against both Open API 3.x
versions. Intentionally left out the enum tests and schema examples
since those will be updated shortly and be different between the two
versions.
4. Added support for `type: "null"` in the 3.1 schema emitter. I
squeezed this change in because the changes involved were actually
really small, and this way TypeScript was happy we were emitting 3.1
schemas that matched the defined interface (no `nullable`). I copied the
behavior that the Json Schema emitter uses for handling nulls.
5. Updated `exclusiveMinimum/Maximum` to be a number value instead of a
boolean to match the Open API 3.1 spec.

Note to reviewers: Hide whitespace - otherwise the test changes will
look monstrous.

---------

Co-authored-by: Christopher Radek <[email protected]>
Implements #5013

Co-authored-by: Christopher Radek <[email protected]>
Implements #5011 
The only place I found this made sense to emit a schema type as a list
currently is with enums as mentioned in the linked issue.

Co-authored-by: Christopher Radek <[email protected]>
@azure-sdk
Copy link
Collaborator

azure-sdk commented Dec 13, 2024

All changed packages have been documented.

  • @typespec/openapi3
Show changes

@typespec/openapi3 - feature ✏️

Adds support for emitting Open API 3.1 models using the openapi-versions emitter configuration option.,> Open API 3.0 is emitted by default.

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 📚 Next docs

@chrisradek chrisradek marked this pull request as ready for review December 16, 2024 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants