Enhancement: the type names in the generated OpenAPI Schema are ugly and unreadable

[hsq125]

Summary

Here is one single example. In Python I have the following class

class SearchFaceMargins(Struct):...

that gets transformed in an unreadable type name like this

GetSetOfEventSearchFaceConfigSearchFaceMarginsResponseBody

altough it should just be something like SearchFaceMargins

I understand that it is an easy strategy to avoid collisions, but too naive, leading to unsable generated code. These type names are unreadable and make the typescript client code also unreadable.

As such, the schema generation in unusable. Is there a possiblity to change that ?

[provinzkraut]

The name by default will be the name of the type:

import msgspec

from litestar import Litestar, get


class Something(msgspec.Struct):
    pass


@get("/")
async def handler() -> Something:
    return Something()


app = Litestar([handler])
print(app.openapi_schema.components.schemas.keys()) # dict_keys(['Something'])

You'll have to be more specific in your report in what you are doing to produce that result. There are many ways to change many aspects of the schema generation, but without know how you've arrived at this point, it's a bit difficult to find a solution.

---

And while I can understand being frustrated about something not working the way you'd like, I would also recommend being a bit more friendly when asking people to dedicate some of their free time to do something you want. It's generally more effective and just a polite thing to do :)