Apply suggestions from code review

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
Travis Ralston 2022-06-08 14:40:41 -06:00 committed by GitHub
parent c02e1f1af9
commit b509444738
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 7 deletions

View file

@ -1878,10 +1878,10 @@ capability to handle relationships.
{{% /boxes/warning %}} {{% /boxes/warning %}}
Relationships which don't match the schema, or which break the rules of a relationship, Relationships which don't match the schema, or which break the rules of a relationship,
are simply ignored. Such an example might be the parent and child being in different are simply ignored. An example might be the parent and child being in different
rooms or the relationship missing properties required by the schema below. The events rooms, or the relationship missing properties required by the schema below. Clients
would appear independent of each other or optionally with an error message (if handling such invalid relationships should show the events independently of each
rendered/handled by the client exclusively). other, optionally with an error message.
{{% boxes/note %}} {{% boxes/note %}}
While this specification describes an `m.relates_to` object containing a `rel_type`, there While this specification describes an `m.relates_to` object containing a `rel_type`, there
@ -1918,12 +1918,12 @@ of times that `key` was used by child events.
The actual aggregation format depends on the `rel_type`. The actual aggregation format depends on the `rel_type`.
{{% boxes/note %}} {{% boxes/note %}}
This specification does not currently describe any `rel_type` which require This specification does not currently describe any `rel_type`s which require
aggregation. This functionality forms a framework for future extensions. aggregation. This functionality forms a framework for future extensions.
{{% /boxes/note %}} {{% /boxes/note %}}
Aggregations are sometimes automatically included by a server alongside the parent Aggregations are sometimes automatically included by a server alongside the parent
event. This This is known as a "bundled aggregation" or "bundle" for simplicity. The event. This is known as a "bundled aggregation" or "bundle" for simplicity. The
act of doing this is "bundling". act of doing this is "bundling".
When an event is served to the client through the APIs listed below, a `m.relations` property When an event is served to the client through the APIs listed below, a `m.relations` property
@ -2035,6 +2035,8 @@ able to accurately aggregate the events.
#### Relationships API #### Relationships API
{{% added-in v="1.3" %}}
To retrieve the child events for a parent from the server, the client can call the To retrieve the child events for a parent from the server, the client can call the
following endpoint. The events returned might require local aggregation by the client, following endpoint. The events returned might require local aggregation by the client,
however if those same events have bundles of their own then they should be present. A however if those same events have bundles of their own then they should be present. A

View file

@ -62,7 +62,7 @@ replies, and MUST strip the fallback before rendering the reply. The
specific fallback text is different for each `msgtype`, however the specific fallback text is different for each `msgtype`, however the
general format for the `body` is: general format for the `body` is:
``` ```text
> <@alice:example.org> This is the original body > <@alice:example.org> This is the original body
This is where the reply goes This is where the reply goes