mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-05-02 07:04:09 +02:00
Compare commits
1 commit
d054acc627
...
69ea5e0345
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
69ea5e0345 |
|
|
@ -1 +0,0 @@
|
||||||
Clarify how to use `state_after` ahead of declaring full support for its spec version.
|
|
||||||
|
|
@ -133,15 +133,10 @@ paths:
|
||||||
sync and the **start** of the timeline in `state` and MUST omit
|
sync and the **start** of the timeline in `state` and MUST omit
|
||||||
`state_after`.
|
`state_after`.
|
||||||
|
|
||||||
Servers MAY implement this parameter ahead of declaring support for
|
Even if this is set to `true`, clients MUST update their local state
|
||||||
the version of the spec in which it was introduced. Consequently,
|
with events in `state` and `timeline` if `state_after` is missing in
|
||||||
clients MAY set this parameter to `true` regardless of the
|
the response, for compatibility with servers that don't support this
|
||||||
[`/versions`](/client-server-api/#get_matrixclientversions) response.
|
parameter.
|
||||||
If they do, they can infer whether the server actually supports this
|
|
||||||
parameter from the presence of `state_after` in the response. If
|
|
||||||
`state_after` is missing, clients MUST behave as if they had not
|
|
||||||
specified the parameter and update their local state with events
|
|
||||||
in `state` and `timeline`.
|
|
||||||
|
|
||||||
By default, this is `false`.
|
By default, this is `false`.
|
||||||
example: false
|
example: false
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue