Fix naming for nested classes

[evroon]

fixes #67

See the docstrings, for nested classes we need to use qualname instead of name. We also need to prepend the module name, because that's what pydantic does as well.

I also updated the sorting to use __qualname__ instead of __name__.

Can be tested with:

from openapi_pydantic import OpenAPI
from openapi_pydantic.util import PydanticSchema, construct_open_api_with_schema_class
from pydantic import BaseModel, Field


def construct_base_open_api() -> OpenAPI:
    return OpenAPI.model_validate(
        {
            "info": {"title": "My own API", "version": "v0.0.1"},
            "paths": {
                "/a": {
                    "post": {
                        "requestBody": {
                            "content": {
                                "application/json": {
                                    "schema": PydanticSchema(schema_class=ResourceA.Body)
                                }
                            }
                        },
                    }
                },
                "/b": {
                    "post": {
                        "requestBody": {
                            "content": {
                                "application/json": {
                                    "schema": PydanticSchema(schema_class=ResourceB.Body)
                                }
                            }
                        },
                    }
                },
            },
        }
    )


class ResourceA:
    class Body(BaseModel):
        a: str


class ResourceB:
    class Body(BaseModel):
        b: str


open_api = construct_base_open_api()
open_api = construct_open_api_with_schema_class(open_api)

print(open_api.model_dump_json(by_alias=True, exclude_none=True, indent=2))

[mike-oakley]

Hey @evroon - thanks for opening this, looks great - would you mind adding a test or two to cover this? 🙏🏼

[evroon]

Sure, I added a test that covers nesting, let me know what you think of it.

[mike-oakley]

Thanks @evroon - looks like the resolver logic has been borked a bit which is breaking the tests. If you can fix the failing checks that would be great and we can get this merged! I rebased to main for you as I've refactored some of the runners for this!

[evroon]

Hmm I looked into it but I am not sure how to fix the remaining tests.

The paths contain references to#/components/schemas/tests__v3_0__test_validated_schema__construct_sample_api___locals___SampleRequest but the definitions are called #/components/schemas/SampleRequest. Not sure where the tests__v3_0__test_validated_schema__construct_sample_api___locals___SampleRequest comes from.

[evroon]

I don't think this is actually possible because it depends on Rust code in pydantic-core which is responsible for the naming of these classes. That naming logic can also be changed in newer versions of pydantic-core so even if you get it right in this PR, it might be broken in the future. I think it makes more sense to just consider nested classes a limitation of this project.