✨ Add support for OpenAPI 3.1.0#9770
Conversation
…of Pydantic bytes fields in v1
… examples the main field
…precated() (already a dependency of Pydantic)
|
📝 Docs preview for commit c719570 at: https://649f03f3c002911c0a8b598b--fastapi.netlify.app |
|
📝 Docs preview for commit 3483b4c at: https://649f1770de745124017bddde--fastapi.netlify.app |
|
📝 Docs preview for commit aad9988 at: https://649f1b6f22c0772d2c878943--fastapi.netlify.app |
|
📝 Docs preview for commit aad9988 at: https://649f1db20103a834d44992e8--fastapi.netlify.app |
|
Hello, Is there a way to downgrade to 3.0 while keeping up to date? |
|
I mean the FastAPI package itself... |
|
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. |
|
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