Python: (de)serialize using Pydantic #4973
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rialization for table metadata
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://github.com/samuelcolvin/pydantic provides data validation and settings management using Python type-hints.
Fast and extensible, pydantic plays nicely with your linters/IDE/brain. Define how data should be in pure, canonical Python 3.7+; validate it with pydantic.
I took the basis from @samredai's PR in #3677
It allows us to easily (de)serialize the
TableMetadataincluding all the nested fields (schema, fields and types). While working on this, I've also noticed some discrepancies with the spec. For example:is_optional, while the spec talks aboutrequiredmap.keyis a field in Python, while in the spec, this is a type.In this PR I also correct some of these discrapencies to avoid confusion among the different implementations. This PR comes with a lot of test to check proper (de)serialization of the tablemetadata, schema and types.
#3677