Clarify that the latest_event field is serialized in the same form as the event itself (#2169)

This commit is contained in:
Benjamin Bouvier 2025-07-22 16:23:28 +02:00 committed by Tom Foster
parent 20eff8b5d6
commit 4d23313e39
2 changed files with 2 additions and 1 deletions

View file

@ -0,0 +1 @@
The `latest_event` in an aggregated set of thread events uses the same format as the event itself.

View file

@ -185,7 +185,7 @@ included under the `m.relations` property in `unsigned` for the thread root. For
``` ```
`latest_event` is the most recent event (topologically to the server) in the thread sent by an `latest_event` is the most recent event (topologically to the server) in the thread sent by an
un-[ignored user](#ignoring-users). un-[ignored user](#ignoring-users). It should be serialized in the same form as the event itself.
Note that, as in the example above, child events of the `latest_event` should Note that, as in the example above, child events of the `latest_event` should
themselves be aggregated and included under `m.relations` for that event. The themselves be aggregated and included under `m.relations` for that event. The