Hey,
I was fiddling with composite data types, in particular with Reference to implement nested schemas, and there seems to be an issue with how arrays and objects of references are serialized when calling dict() on the parent class.
Consider the following schemas:
import typesystem as ts
class Child(ts.Schema):
pass
class ParentA(ts.Schema):
child = ts.Reference(to=Child)
class ParentB(ts.Schema):
children = ts.Array(ts.Reference(Child))
class ParentC(ts.Schema):
children = ts.Object(properties=ts.Reference(Child))
Test cases with what should happen IMO:
pa = ParentA(child=Child())
assert dict(pa) == {"child": {}} # OK
pb = ParentB(children=[Child()])
assert dict(pb) == {"children": [{}]} # FAIL
# {"children": [Child()]}
pc = ParentC(children=[Child()])
assert dict(pc) == {"children": {"john": {}}} # FAIL
# {"children": {"john": Child()}}
This causes issues when passing the result of dict(pb) or dict(pc) to, say, json.dumps(), because it gets Child instances which are not JSON-serializable.
Am I simply abusing Array and Object? Is there another way of implementing composite fields with nested schemas?
Hey,
I was fiddling with composite data types, in particular with
Referenceto implement nested schemas, and there seems to be an issue with how arrays and objects of references are serialized when callingdict()on the parent class.Consider the following schemas:
Test cases with what should happen IMO:
This causes issues when passing the result of
dict(pb)ordict(pc)to, say,json.dumps(), because it getsChildinstances which are not JSON-serializable.Am I simply abusing
ArrayandObject? Is there another way of implementing composite fields with nested schemas?