mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
33624fc2fa
There's a FastAPI bug that results in the OpenAPI spec outputting the same operation id for each operation when specifying multiple HTTP methods. - Discussion: https://github.com/tiangolo/fastapi/discussions/8449 - Pending PR to fix: https://github.com/tiangolo/fastapi/pull/10694 In our case, we have a `get_image_full` endpoint that handles GET and HEAD. This results in an invalid OpenAPI schema. A workaround is to use two route decorators for the operation handler. This works as expected - HEAD requests get the header, and GET requests get the resource. And the OpenAPI schema is valid.