Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-28 22:14:10 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Add missing bits of MSC2675

Browse source
This commit is contained in:
Travis Ralston 2022-05-26 21:19:02 -06:00
parent 532b06b25d
commit 9fa50a75ca
1 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
content/client-server-api/_index.md
View file

@ -1978,6 +1978,11 @@ Note how the `org.example.possible_annotations` bundle is an array compared to t
the relationship in a single object. Both are valid bundles, and their exact types the relationship in a single object. Both are valid bundles, and their exact types
depend on the `rel_type`. depend on the `rel_type`.
{{% boxes/warning %}}
State events do not currently receive the `m.relations` unsigned field. This is not
necessarily a deliberate design decision, and MSCs which aim to fix this are welcome.
{{% /boxes/warning %}}
The endpoints where the server *should* include the `m.relations` unsigned field are: The endpoints where the server *should* include the `m.relations` unsigned field are:
* [`GET /rooms/{roomId}/messages`](#get_matrixclientv3roomsroomidmessages) * [`GET /rooms/{roomId}/messages`](#get_matrixclientv3roomsroomidmessages)
@ -1998,12 +2003,11 @@ time of handling, the client should continue to aggregate locally if it is aware
the relationship type's behaviour. For example, a client might increment a `count` the relationship type's behaviour. For example, a client might increment a `count`
on a parent event's bundle if it saw a new child event which referenced that parent. on a parent event's bundle if it saw a new child event which referenced that parent.
{{% boxes/warning %}} The bundle provided by the server only includes child events which were known at the
The bundle provided by the server only includes events which were known at the time time the client would receive the bundle. For example, in a single `/sync` response
the event was *received*. This can mean that in a single `/sync` response an event with the parent and multiple child events the child events would have already been
will have a bundle and more events which qualify for that aggregation: in this case, included on the parent's `m.relations` field. Events received in future syncs would
the client *should* aggregate the events which are "after" the event in question on need to be aggregated manually by the client.
its own, as the server will not have considered them.
{{% /boxes/warning %}} {{% /boxes/warning %}}
{{% boxes/note %}} {{% boxes/note %}}