Closed ric-evans closed 3 years ago
Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.
We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.
Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.
We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.
We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR
Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.
We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.
We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR
Fair enough.
Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.
We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.
We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR
Fair enough.
schema/types.py
containing metadata type hintsvalidation.py
to validate metadata using introspection (future)validation.py
toschema/validation.py