Certain advanced arbitrary types are properly supported in our SerDes protocol, but fail when attached to a class definition. This resolves those issues and adds tests using the pandas library.
This resolves 75
2.0.10
In certain cases a name wasn't passed on during finalization of nested objects or arrays. This is now resolved.
2.0.9
As a result of expanding support for sub-types, there were a few disparate methods in use to determine which parent-type to use for certain operations. Namely, this resulted in incompatibility between the Constraints system and the Schema system.
This release introduces a unified approach to resolving parent-type which guarantees a more consistent resolution across systems.
2.0.8
Expanding support of subclassed builtins resulted in unexpected and potentially broken behavior when generating schema/constraints for those objects. This release resolves those issues with explicit behavior for those cases.
2.0.7
Changes:
* Bugfix: Collision in translator for classes with the same name (66 ) * Bugfix: Support subclasses of known formats in schema gen (67 ) * Improvement: Support defaultdict (67 )
2.0.6
Previously, we only allowed for unknown fields with primitive data when the fields_out & fields_in for an object didn't match.
Additionally, we didn't allow for translation from a source with a small signature, but matching fields.