mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-26 13:04:10 +01:00
Update content/client-server-api/modules/event_replacements.md
This commit is contained in:
parent
091d1f032c
commit
943b5f72f4
|
|
@ -131,10 +131,13 @@ ratchet entry should **not** be re-used.
|
|||
|
||||
#### Applying `m.new_content`
|
||||
|
||||
When applying a replacement, the `content` of the original event is replaced
|
||||
entirely by the `m.new_content` from the replacement event, with the exception
|
||||
of `m.relates_to`, which is left *unchanged*. (Any `m.relates_to` property
|
||||
within `m.new_content` should be ignored.)
|
||||
When applying a replacement, the `content` of the original event is treated as
|
||||
being overwritten entirely by `m.new_content`, with the exception of `m.relates_to`,
|
||||
which is left *unchanged*. Any `m.relates_to` property within `m.new_content`
|
||||
is ignored. (Note that server implementations must not *actually* overwrite
|
||||
the original event's `content`: instead the server presents it as being overwritten
|
||||
when it is served over the client-server API. See [Server-side replacement of content](#server-side-replacement-of-content)
|
||||
below.)
|
||||
|
||||
For example, given a pair of events:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue