From fb4a0d8f66fb6263786ab7c4de3ef21517fcc64c Mon Sep 17 00:00:00 2001 From: Benjamin Bouvier Date: Tue, 22 Jul 2025 16:23:28 +0200 Subject: [PATCH] Clarify that the `latest_event` field is serialized in the same form as the event itself (#2169) --- changelogs/client_server/newsfragments/2169.clarification | 1 + content/client-server-api/modules/threading.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelogs/client_server/newsfragments/2169.clarification diff --git a/changelogs/client_server/newsfragments/2169.clarification b/changelogs/client_server/newsfragments/2169.clarification new file mode 100644 index 00000000..49648401 --- /dev/null +++ b/changelogs/client_server/newsfragments/2169.clarification @@ -0,0 +1 @@ +The `latest_event` in an aggregated set of thread events uses the same format as the event itself. diff --git a/content/client-server-api/modules/threading.md b/content/client-server-api/modules/threading.md index 5fedbcf8..9f87920a 100644 --- a/content/client-server-api/modules/threading.md +++ b/content/client-server-api/modules/threading.md @@ -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 -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 themselves be aggregated and included under `m.relations` for that event. The