#[non_exhaustive]pub enum Relation {
    Reply {
        in_reply_to: InReplyTo,
    },
    Replacement(Replacement),
    Reference(Reference),
    Annotation(Annotation),
    Thread(Thread),
}events only.Expand description
Relationship information about an encrypted event.
Outside of the encrypted payload to support server aggregation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
Reply
An m.in_reply_to relation indicating that the event is a reply to another event.
Replacement(Replacement)
An event that replaces another event.
Reference(Reference)
A reference to another event.
Annotation(Annotation)
An annotation to an event.
Thread(Thread)
An event that belongs to a thread.
Implementations§
Source§impl Relation
 
impl Relation
Sourcepub fn rel_type(&self) -> Option<RelationType>
 
pub fn rel_type(&self) -> Option<RelationType>
The type of this Relation.
Returns an Option because the Reply relation does not have arel_type field.
Sourcepub fn data(&self) -> Cow<'_, Map<String, Value>>
 
pub fn data(&self) -> Cow<'_, Map<String, Value>>
The associated data.
The returned JSON object holds the contents of m.relates_to, including rel_type and
event_id if present, but not things like m.new_content for m.replace relations that
live next to m.relates_to.
Prefer to use the public variants of Relation where possible; this method is meant to
be used for custom relations only.