Make clear the thread root is not in the thread (#1677)
* Make clear the thread root is not in the thread Signed-off-by: Andy Balaam <andy.balaam@matrix.org> * Changlog entry for thread PR 1677 - thread roots not in thread * Fix typo * Add formatting for code values. Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com> * Reword main timeline ID paragraph * Use close to the original wording for the 'recurse' part of the 'in the thread' definition * Remove note about thread roots being displayed in a thread * Define the thread root --------- Signed-off-by: Andy Balaam <andy.balaam@matrix.org> Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
This commit is contained in:
parent
634b24fb25
commit
6fe2ff4fa7
4 changed files with 29 additions and 24 deletions
|
@ -12,11 +12,11 @@ as by providing some context to what is going on in the thread but keeping the f
|
|||
history behind a disclosure.
|
||||
|
||||
Threads are established using a `rel_type` of `m.thread` and reference the
|
||||
*thread root* (the first event in a thread). It is not possible to create a
|
||||
thread from an event which itself is the child of an event relationship (i.e.,
|
||||
one with an `m.relates_to` property). It is therefore also not possible to nest
|
||||
threads. All events in a thread reference the thread root instead of the
|
||||
most recent message, unlike rich reply chains.
|
||||
*thread root* (the main timeline event to which the thread events refer). It is not possible to create a thread from an event which itself
|
||||
is the child of an event relationship (i.e., one with an `m.relates_to`
|
||||
property). It is therefore also not possible to nest threads. All events in a
|
||||
thread reference the thread root instead of the most recent message, unlike rich
|
||||
reply chains.
|
||||
|
||||
As a worked example, the following represents a thread and how it would be formed:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue