Compare commits

...

2 commits

Author SHA1 Message Date
Doug 7eed5134d1
Merge 4842d9e9aa into 935c23485b 2025-11-18 10:56:58 +00:00
Johannes Marbach 935c23485b
Clarify how to use state_after ahead of declaring full support for its spec version (#2240) 2025-11-18 10:56:22 +00:00
2 changed files with 10 additions and 4 deletions

View file

@ -0,0 +1 @@
Clarify how to use `state_after` ahead of declaring full support for its spec version.

View file

@ -133,10 +133,15 @@ 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`.
Even if this is set to `true`, clients MUST update their local state Servers MAY implement this parameter ahead of declaring support for
with events in `state` and `timeline` if `state_after` is missing in the version of the spec in which it was introduced. Consequently,
the response, for compatibility with servers that don't support this clients MAY set this parameter to `true` regardless of the
parameter. [`/versions`](/client-server-api/#get_matrixclientversions) response.
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