Docs Preview

@dmontagu To not lose themodel_dump[_json] methods and maintain backward compatibility (at least of theBaseModel bits we think people are likely to use), would it be crazy to implement them explicitly on the classes in question, delegating to theTypeAdapter?

I could imagine a decorator that works on any dataclass and does just that -- that may be useful more generally to get consistent validation/serialization APIs betweenBaseModels and dataclasses.

I thought about that but the reason I didn't do it is because it won't be type-aware (well, specifically, aware of the generic parameters involved; they willalways beAny), so may end up with some surprising behavior. Admittedly it would be compatible with the way things work now, but I also feel it's a bit confusing to havemodel_X methods on a dataclass, it might make you think it's not actually a dataclass. Given we aren't in v1 yet and most people aren't manually serializing the reports, my feeling is it's not unreasonable to make a breaking change here and just make it a proper dataclass now.

If peopleare making serious use ofmodel_dump etc. on the ReportCase / EvaluationReport classes then I might feel differently, but I would be surprised if that was the case and I'm not sure we have a good way to determine that anyway (short of user feedback, which I assume we won't get until breaking their code 😞).