Add support for Pydantic model validation/serialization (fixes #8751) #9023
+311
−17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow validation of arguments using Pydantic, as well as result serialization. This PR would fix (IMHO) #8751.
With this PR, you can pass
pydantic=True
to a task decorator. If set, any argument type hinted as a Pydantic model will be validated (note: this means data validation and loading into the model class Pydantic speak) to that model, and any result matching a return type annotation will automatically be converted to a dict (usingmodel_dump()
).With this feature, tasks look a lot more like FastAPI endpoints, where query arguments, request and response bodies are validated/serialized using Pydantic. The advantage is of course automatic data validation and safer typing. mypy will catch type hinting errors, and IDEs auto-complete values in the models.