Right now, you need an object type Guid (as the input to RelativityObjectAttribute to define a Gravity class . This excludes all non-dynamic object types, such as saved searches and fields, from being present in a Gravity model as associated objects. At @Milyli, these field types frequently show up in configuration RDOs, limiting Gravity's usefulness.
We should allow object type to be defined by an ArtifactType as well for these scenarios (e.g. [RelativityObject(14)] for a field).
The fields themselves have Guids, so the other attributes would not need new overloads.
This might be easier to do after #158.
Right now, you need an object type Guid (as the input to
RelativityObjectAttributeto define a Gravity class . This excludes all non-dynamic object types, such as saved searches and fields, from being present in a Gravity model as associated objects. At @Milyli, these field types frequently show up in configuration RDOs, limiting Gravity's usefulness.We should allow object type to be defined by an ArtifactType as well for these scenarios (e.g.
[RelativityObject(14)]for a field).The fields themselves have Guids, so the other attributes would not need new overloads.
This might be easier to do after #158.