Make sure that repr of entity types can actually be pickled/unpickled

Description

More generally, revisit how we represent values returned by the Python client so that they can be used with that Python programmers consider to be standard. It's up to the issue assignee to recommend whether "pickling" is such a tool.

Environment

None

Activity

Show:
Meredith Slota
October 3, 2018, 10:41 PM

Related to refactor/testing coverage.

Ziming Dong
June 15, 2017, 12:07 AM

Just tried repr() on a File entity and had these issues:
There's an issue with concreteTypes said to be defined multiple times in the superclases's _init_: reason unknown
'annotations' is used in the constructor as a way to define the entity's annotations, but there is also a properties.annotations which specifies a path to the annotations service for that entity. solution: in _repr_ make it print out "File(...., properties={annotations:"path/to/service", ....},...)" instead of "File(....., annotations='path/to/service/, ...)"

Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Jordan Kiang

Reporter

Larsson Omberg

Labels