Use inline code for endpoints and add link to /members definition

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
Kévin Commaille 2026-03-30 16:45:45 +02:00
parent 7dad9ebc43
commit b770ac81a1
No known key found for this signature in database
GPG key ID: F26F4BE20A08255B

View file

@ -3120,19 +3120,20 @@ events they have already been sent, and choose to skip sending membership
events for members whose membership has not changed. These are called events for members whose membership has not changed. These are called
'redundant membership events'. Clients may request that redundant membership 'redundant membership events'. Clients may request that redundant membership
events are always included in responses by setting `include_redundant_members` events are always included in responses by setting `include_redundant_members`
to true in the filter. to `true` in the filter.
The expected pattern for using lazy-loading is currently: The expected pattern for using lazy-loading is currently:
- Client performs an initial /sync with lazy-loading enabled, and - Client performs an initial `/sync` with lazy-loading enabled, and
receives only the membership events which relate to the senders of receives only the membership events which relate to the senders of
the events it receives. the events it receives.
- Clients which support display-name tab-completion or other - Clients which support display-name tab-completion or other
operations which require rapid access to all members in a room operations which require rapid access to all members in a room
should call /members for the currently selected room, with an `?at` should call [`/members`](#get_matrixclientv3roomsroomidmembers) for
parameter set to the /sync response's from token. The member list the currently selected room, with an `?at` parameter set to the
for the room is then maintained by the state in subsequent `/sync` response's `from` token. The member list for the room is
incremental /sync responses. then maintained by the state in subsequent incremental `/sync`
responses.
- Clients which do not support tab-completion may instead pull in - Clients which do not support tab-completion may instead pull in
profiles for arbitrary users (e.g. read receipts, typing profiles for arbitrary users (e.g. read receipts, typing
notifications) on demand by querying the room state or [`/profile`](#get_matrixclientv3profileuserid). notifications) on demand by querying the room state or [`/profile`](#get_matrixclientv3profileuserid).