Prep for pydantic Artifacts/Producers#71
Conversation
JacobHayes
commented
Jul 27, 2021
- Rename schema -> type to avoid pydantic collision
- Rename {Format,Storage}.validate_artifact -> .supports
- Make Models frozen by default and add stricter type checking (pydantic parses)
Codecov Report
@@ Coverage Diff @@
## golden #71 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 685 699 +14
Branches 79 81 +2
=========================================
+ Hits 685 699 +14
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
I like the name change away from schema, but is there any chance of confusion that a.type and type(a) are totally different, despite seemingly similar naming? Note that this does not occur with pd.DataFrame.dtypes, since that attribute dtypes: (a) is not named type; (b) exactly corresponds to the numpy data types.
That is to say, if there's something else that is neither schema nor type, it might be worth considering (but then, of course, Type and TypeSystem and TypeAdapter would merit another look as well).
8105903 to
fd4a630
Compare
I don't think too much(🤞),
Yeah, I was trying to think of this, but nothing came up. |