pub struct EntityDetailDto {
pub entity_id: String,
pub entity_type_id: u32,
pub canonical_name: String,
pub aliases: Vec<String>,
pub mention_count: u32,
pub created_at_unix_nanos: u64,
pub updated_at_unix_nanos: u64,
pub merged_into: Option<String>,
pub resolved_from: Vec<String>,
}Expand description
A read-side entity view in the public JSON contract. Ids are UUID strings.
Fields§
§entity_id: StringThe entity id (UUID).
entity_type_id: u32Registered type id (0 = none/unknown).
canonical_name: StringCanonical display name.
aliases: Vec<String>Known aliases.
mention_count: u32How many memories mention this entity.
created_at_unix_nanos: u64Creation time (unix nanos).
updated_at_unix_nanos: u64Last-update time (unix nanos).
merged_into: Option<String>Survivor id (UUID) if merged away; null otherwise.
resolved_from: Vec<String>Merge-redirect chain walked by ENTITY_GET to reach this (surviving)
entity, oldest first, EXCLUDING the survivor itself. Empty on a direct
hit (the requested id was live) and on list/create responses, which
carry no redirect chain. For A → B → C, GET /v1/entities/A returns
entity C with resolved_from = ["A", "B"].
Implementations§
Source§impl EntityDetailDto
impl EntityDetailDto
Sourcepub fn from_get_response(resp: EntityGetResponse) -> Self
pub fn from_get_response(resp: EntityGetResponse) -> Self
Build from an ENTITY_GET response, surfacing the merge-redirect chain
(resolved_from) that a plain EntityView does not carry.