Missing HTTP response codes in OpenAPI schema #763
Labels
enhancement
New feature or request
OPTIMADE v1.0
A label for tagging issues/PRs that are required for compliance with v1.0 of the OPTIMADE spec
schema
Concerns the schema models
server
Issues pertaining to the example server implementation
suggestions
While trying out the schemathesis library for fuzzy API testing based on schemas, I discovered that the response codes we provide in the OpenAPI schemas are limited.
I guess we need to somehow we make our exceptions handlers known to FastAPI? It seems like there is something a bit strange with our
ErrorResponse
being a valid "successful response", presumably because of the way we use our exception handlers. See e.g. for the links endpoint:It would be nice to add e.g.
553 VersionNotSupported
and other errors that are buried in the spec so that automated tools can use our API more effectively.The text was updated successfully, but these errors were encountered: