Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Comments

✨ Add support for OpenAPI 3.1.0#9770

Merged
tiangolo merged 34 commits intomasterfrom
openapi-3-1-0
Jun 30, 2023
Merged

✨ Add support for OpenAPI 3.1.0#9770
tiangolo merged 34 commits intomasterfrom
openapi-3-1-0

Conversation

@tiangolo
Copy link
Member

✨ Add support for OpenAPI 3.1.0

@tiangolo
Copy link
MemberAuthor

📝 Docs preview for commitc719570 at:https://649f03f3c002911c0a8b598b--fastapi.netlify.app

@tiangolo
Copy link
MemberAuthor

📝 Docs preview for commit3483b4c at:https://649f1770de745124017bddde--fastapi.netlify.app

@tiangolotiangolo marked this pull request as ready for reviewJune 30, 2023 18:11
@tiangolo
Copy link
MemberAuthor

📝 Docs preview for commitaad9988 at:https://649f1b6f22c0772d2c878943--fastapi.netlify.app

@tiangolo
Copy link
MemberAuthor

📝 Docs preview for commitaad9988 at:https://649f1db20103a834d44992e8--fastapi.netlify.app

@francipvb
Copy link

Hello,

Is there a way to downgrade to 3.0 while keeping up to date?

soundstripe, arseniiarsenii, cirezd, monometa, edziegle, and jvnte reacted with thumbs up emoji

@francipvb
Copy link

I mean the FastAPI package itself...

@wlievens
Copy link

Is there a way to use recent FastAPI releases but emit v3.0 OpenAPI? I'm using OpenAPITools openapi-generator and they do not fully support v3.1 yet.

durandmiller, nicktimko, Ziqi-Yang, illeatmyhat, and jvnte reacted with thumbs up emoji

@felix-hilden
Copy link

Looking through the code, it seems that there is no way to do that unfortunately. The OpenAPI versions set in the code are only directly forwarded to the spec content instead of determining how it's generated.


A little awkward for me and I'm sure many others who committed to Pydantic 2 as well, because that now clashes :P But for me it seems to be mostly about transforming how optional types are represented so maybe there's a semi-easy way to do it by hand after generating the spec.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@tiangolo@francipvb@wlievens@felix-hilden

[8]ページ先頭

©2009-2026 Movatter.jp