model_config moved to one top class

[Rogalek]

Right now when we use some parameters during model generation (for example --extra-fields=forbid) we will get this:

class ModelA(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    fieldA: Annotated[
        fieldA, Field(description="The filed name of the field")
    ]


class ModelB(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    fieldB: Annotated[
        int,
        Field(description="The field B number", ge=1, le=63),
    ]


class ModelC(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    page: Annotated[
        str,

And this pattern follow for as many openapi models we have.

Could we maybe do something like this? Lets keep the code DRY.

class ProjectBaseModel(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )

class ModelA(ProjectBaseModel):
    fieldA: Annotated[
        fieldA, Field(description="The filed name of the field")
    ]

class ModelB(ProjectBaseModel):
    fieldB: Annotated[
        int,
        Field(description="The field B number", ge=1, le=63),
    ]

class ModelC(ProjectBaseModel):
    page: Annotated[
        str,

[ilovelinux]

Hi, thanks for reporting the issue! Please add the version of datamodel-code-generator you're currently using as it will help us to keep tracking of it.

---

As you noticed, we don't currently support that. I feel it may be not as easy as it looks.

A potential workaround is replacing --extra-fields=forbid with a custom BaseModel (with model_config = ConfigDict(extra="forbid")) and referenced using --base-class CLI argument.

E.g.

# myprojectbasemodel.py
class ProjectBaseModel(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )

Then run:

datamodel-codegen  --base-class ProjectBaseModel [...]

Tip

If you need to import ProjectBaseModel, you can use --additional-imports