mirror of
https://github.com/kennethreitz/pydantic.git
synced 2026-06-05 23:00:18 +00:00
PrettyWood
c83156d0e0
* feat: pydantic dataclasses support built-in ones closes #744 * feat: improve dataclass typing * feat: add support for nested dataclasses closes #1743 * feat: support dataclass schema with nested dataclasses * refactor: remove `_dataclass_with_validation` function * docs: add docstring for `make_dataclass_validator` * refactor: rename DataclassType into Dataclass The name `DataclassType` was missleading as it's not a `Type` per say. * refactor: change global `dataclass` import to local pydantic import time was improved in https://github.com/samuelcolvin/pydantic/pull/1132 by keeping `dataclass` import local. So let's keep it that way! * test: add extra nested case with BaseModel * chore: s/pydantic/_pydantic_/g * docs: add some documentation
100 lines
3.8 KiB
Markdown
100 lines
3.8 KiB
Markdown
If you don't want to use _pydantic_'s `BaseModel` you can instead get the same data validation on standard
|
|
[dataclasses](https://docs.python.org/3/library/dataclasses.html) (introduced in python 3.7).
|
|
|
|
Dataclasses work in python 3.6 using the [dataclasses backport package](https://github.com/ericvsmith/dataclasses).
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_main.py!}
|
|
```
|
|
_(This script is complete, it should run "as is")_
|
|
|
|
!!! note
|
|
Keep in mind that `pydantic.dataclasses.dataclass` is a drop-in replacement for `dataclasses.dataclass`
|
|
with validation, **not** a replacement for `pydantic.BaseModel` (with a small difference in how [initialization hooks](#initialize-hooks) work). There are cases where subclassing
|
|
`pydantic.BaseModel` is the better choice.
|
|
|
|
For more information and discussion see
|
|
[samuelcolvin/pydantic#710](https://github.com/samuelcolvin/pydantic/issues/710).
|
|
|
|
You can use all the standard _pydantic_ field types, and the resulting dataclass will be identical to the one
|
|
created by the standard library `dataclass` decorator.
|
|
|
|
The underlying model and its schema can be accessed through `__pydantic_model__`.
|
|
Also, fields that require a `default_factory` can be specified by a `dataclasses.field`.
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_default_schema.py!}
|
|
```
|
|
_(This script is complete, it should run "as is")_
|
|
|
|
`pydantic.dataclasses.dataclass`'s arguments are the same as the standard decorator, except one extra
|
|
keyword argument `config` which has the same meaning as [Config](model_config.md).
|
|
|
|
!!! warning
|
|
After v1.2, [The Mypy plugin](/mypy_plugin.md) must be installed to type check _pydantic_ dataclasses.
|
|
|
|
For more information about combining validators with dataclasses, see
|
|
[dataclass validators](validators.md#dataclass-validators).
|
|
|
|
## Nested dataclasses
|
|
|
|
Nested dataclasses are supported both in dataclasses and normal models.
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_nested.py!}
|
|
```
|
|
_(This script is complete, it should run "as is")_
|
|
|
|
Dataclasses attributes can be populated by tuples, dictionaries or instances of the dataclass itself.
|
|
|
|
## Stdlib dataclasses and _pydantic_ dataclasses
|
|
|
|
Stdlib dataclasses (nested or not) can be easily converted into _pydantic_ dataclasses by just decorating
|
|
them with `pydantic.dataclasses.dataclass`.
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_stdlib_to_pydantic.py!}
|
|
```
|
|
_(This script is complete, it should run "as is")_
|
|
|
|
Bear in mind that stdlib dataclasses (nested or not) are **automatically converted** into _pydantic_ dataclasses
|
|
when mixed with `BaseModel`!
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_stdlib_with_basemodel.py!}
|
|
```
|
|
_(This script is complete, it should run "as is")_
|
|
|
|
## Initialize hooks
|
|
|
|
When you initialize a dataclass, it is possible to execute code *after* validation
|
|
with the help of `__post_init_post_parse__`. This is not the same as `__post_init__`, which executes
|
|
code *before* validation.
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_post_init_post_parse.py!}
|
|
```
|
|
_(This script is complete, it should run "as is")_
|
|
|
|
Since version **v1.0**, any fields annotated with `dataclasses.InitVar` are passed to both `__post_init__` *and*
|
|
`__post_init_post_parse__`.
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_initvars.py!}
|
|
```
|
|
_(This script is complete, it should run "as is")_
|
|
|
|
### Difference with stdlib dataclasses
|
|
|
|
Note that the `dataclasses.dataclass` from python stdlib implements only the `__post_init__` method since it doesn't run a validation step.
|
|
|
|
When substituting usage of `dataclasses.dataclass` with `pydantic.dataclasses.dataclass`, it is recommended to move the code executed in the `__post_init__` method to the `__post_init_post_parse__` method, and only leave behind part of code which needs to be executed before validation.
|
|
|
|
## JSON Dumping
|
|
|
|
_Pydantic_ dataclasses do not feature a `.json()` function. To dump them as JSON, you will need to make use of the `pydantic_encoder` as follows:
|
|
|
|
```py
|
|
{!.tmp_examples/dataclasses_json_dumps.py!}
|
|
```
|