Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork8.7k
Comments
Conversation
…of Pydantic bytes fields in v1
… examples the main field
…precated() (already a dependency of Pydantic)
tiangolo commentedJun 30, 2023
📝 Docs preview for commitc719570 at:https://649f03f3c002911c0a8b598b--fastapi.netlify.app |
tiangolo commentedJun 30, 2023
📝 Docs preview for commit3483b4c at:https://649f1770de745124017bddde--fastapi.netlify.app |
tiangolo commentedJun 30, 2023
📝 Docs preview for commitaad9988 at:https://649f1b6f22c0772d2c878943--fastapi.netlify.app |
tiangolo commentedJun 30, 2023
📝 Docs preview for commitaad9988 at:https://649f1db20103a834d44992e8--fastapi.netlify.app |
francipvb commentedSep 6, 2023
Hello, Is there a way to downgrade to 3.0 while keeping up to date? |
francipvb commentedSep 6, 2023
I mean the FastAPI package itself... |
wlievens commentedNov 7, 2023
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. |
felix-hilden commentedFeb 3, 2025
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. |
✨ Add support for OpenAPI 3.1.0