-
Notifications
You must be signed in to change notification settings - Fork 226
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
Emit OpenAPI 3.1 compliant specifications #1698
Comments
This feature is something our team was looking into. We are hoping to be able to configure the version. |
Hello, any news on this subject? We are quite interested :) |
Pinging for updates. This is the only thing preventing our team from adopting TypeSpec. |
I'm super excited about TypeSpec, but this and #2463 are blockers for us. They both seem important for the general adoption of TypeSpec. I'm a bit surprised that this is not supported already as OpenAPI 3.1 has been out there for a few years. |
👍 glad to see it's added to this December milestone |
We need to properly emit an standard compliant OpenAPI 3.1 API definition from TypeSpec.
Items to take into account
type: null
The text was updated successfully, but these errors were encountered: