DocumentationAPI reference
Rust · 0.1.0
MemoRelation
REFERENCE links are mutable; COMMENT records immutable creation context.
How relations are written
Use SetMemoRelations or a relations update mask for the complete outgoing REFERENCE set. Identify targets with relatedMemo.name. CreateMemoComment is the only route here that establishes COMMENT context. Deleting one memo removes incident edges but does not recursively delete other memos.
Where this schema is used
These links are derived from direct references in the protocol snapshot. Follow the calling operation for authentication, accepted fields and runtime behavior; a reusable resource schema is not by itself a complete write request.
Referenced by these component schemas:
Shape and fields
object
| Field | Type / requirement | Description |
|---|---|---|
memo | allOf MemoRelation_Memo Required | The memo in the relation. |
relatedMemo | allOf MemoRelation_Memo Required | The related memo. |
type | string (enum)TYPE_UNSPECIFIED · REFERENCE · COMMENTRequired |
Complete schema
Use this complete JSON definition for constraints and nested structure. A field's presence here does not mean it is writable by every caller.
{
"required": [
"memo",
"relatedMemo",
"type"
],
"type": "object",
"properties": {
"memo": {
"allOf": [
{
"$ref": "#/components/schemas/MemoRelation_Memo"
}
],
"description": "The memo in the relation."
},
"relatedMemo": {
"allOf": [
{
"$ref": "#/components/schemas/MemoRelation_Memo"
}
],
"description": "The related memo."
},
"type": {
"enum": [
"TYPE_UNSPECIFIED",
"REFERENCE",
"COMMENT"
],
"type": "string",
"format": "enum"
}
}
}