Bug: openapi spec. generation does not respect Response status_code about litestar HOT 2 CLOSED

In case you are not aware, you can do this explicitly by configuring responses as shown in https://docs.litestar.dev/latest/usage/openapi/schema_generation.html.

Question to you. In your example it is just one response that is being returned, what if your route handler has more than one return, like the following. Having to parse the function body to retrieve this would be an overhead. I do not think this is an overhead the framework has to do, with this context, would you still consider this a bug?

if some_condition:
    return Response(
        {"detail": "Test succesfull"},
        status_code=HTTP_200_OK,
    )
elif some_other_condition:
    return Response(
        {"detail": "Test succesfull"},
        status_code=HTTP_201_CREATED,
    )
elif not_found:
    return Response(
        {"detail": "not found"},
        status_code=HTTP_404_NOT_FOUND,
    )

from litestar.

@TheZwieback as @Alc-Alcb explained, this is not really a bug. Litestar does not know what you're doing inside your functions, so you'll have to tell it.

You can set the status code on the handler like so

@post("/test", status_code=HTTP_200_OK)
async def test() -> Response[dict[str, str]]:
    return Response(
        {"detail": "Test succesfull"},
        status_code=HTTP_200_OK,
    )

which should do what you're looking for :)

from litestar.