Set/override config options when calling .validate()

[gwerbin]

Often I want to reuse the same schema/model for multiple different purposes.

When loading data from an outside source, I want to run parsers, including the built-in type coercion, and set strict=False to avoid crashing at runtime due to the presence of extra columns that I don't care about. But when running my unit tests, I want strict=True to assert that extra columns are not present, but I do not want to run any parsers or coercion.

In the current setup, I need to create separate schemas/models with different configs for different purposes, and that's very verbose.

Currently I have to write this:

class _WidgetBaseModel(DataFrameModel):
    foo_id: Index[int] = Field(check_name=True)
    width: Series[float]
    height: Series[float]

class WidgetInputModel(_WidgetBaseModel):
    class Config:
        strict = False
        coerce = True

class WidgetOutputModel(_WidgetBaseModel):
    class Config:
        strict = True
        coerce = False

WidgetInputModel.validate(df)  # strict=False, coerce=True
WidgetOutputModel.validate(df)  # strict=True, coerce=False

But I want to be able to write this:

class WidgetModelBase(DataFrameModel):
    foo_id: Index[int] = Field(check_name=True)
    width: Series[float]
    height: Series[float]

WidgetModelBase.validate(df, strict=False, coerce=True)
WidgetModelBase.validate(df, strict=True, coerce=False)

The examples above use the class-based "model" syntax, but this request applies equally to the functional "schema" syntax as well.