Compare commits

...

9 commits

Author SHA1 Message Date
Johannes Marbach 3dd4b40aed
Update data/api/client-server/definitions/public_rooms_chunk.yaml
Co-authored-by: Kévin Commaille <76261501+zecakeh@users.noreply.github.com>
2025-04-30 08:57:11 +02:00
Johannes Marbach 469f32821c
Update content/client-server-api/modules/search.md 2025-04-30 08:56:29 +02:00
Johannes Marbach e9e937ca56
Update content/client-server-api/modules/search.md 2025-04-30 08:56:00 +02:00
Johannes Marbach a3f40730ed
Update data/api/client-server/create_room.yaml
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
2025-04-30 08:55:05 +02:00
Johannes Marbach 39edd64034
Update data/event-schemas/schema/components/m_text_content_block.yaml 2025-04-30 08:54:32 +02:00
Johannes Marbach 51a4bbc1d9
Update data/api/client-server/create_room.yaml 2025-04-30 08:53:36 +02:00
Johannes Marbach 22a8066ed2
Update data/api/client-server/create_room.yaml 2025-04-30 08:52:29 +02:00
Johannes Marbach 9a1495f869
Update data/api/client-server/create_room.yaml 2025-04-30 08:52:03 +02:00
Johannes Marbach 8df093056f
Rephrase usage of topics in server-side search
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
2025-04-30 08:50:47 +02:00
4 changed files with 14 additions and 14 deletions

View file

@ -26,10 +26,10 @@ on certain keys of certain event types.
The supported keys to search over are:
- `content.body` in [`m.room.message`](#mroommessage)
- `content.name` in [`m.room.name`](#mroomname)
- `content.topic` as well as the `body` of the `text/plain` representation
in [`m.room.topic`](#mroomtopic)
- `content.body` in [`m.room.message`](/client-server-api/#mroommessage)
- `content.name` in [`m.room.name`](/client-server-api/#mroomname)
- In [`m.room.topic`](/client-server-api/#mroomtopic), `content.topic`
as well as the `body` of the `text/plain` representation in `content['m.topic']`.
The search will *not* include rooms that are end to end encrypted.

View file

@ -109,17 +109,17 @@ paths:
name:
type: string
description: |-
If this is included, an [`m.room.name`](#mroomname) event
If this is included, an [`m.room.name`](/client-server-api/#mroomname) event
will be sent into the room to indicate the name for the room.
This overwrites any [`m.room.name`](#mroomname) event in
`initial_state`.
This overwrites any [`m.room.name`](/client-server-api/#mroomname)
event in `initial_state`.
topic:
type: string
description: |-
If this is included, an [`m.room.topic`](#mroomtopic) event
with a `text/plain` mimetype will be sent into the room to
indicate the topic for the room. This overwrites any
[`m.room.topic`](#mroomtopic) event in `initial_state`.
If this is included, an [`m.room.topic`](/client-server-api/#mroomtopic)
event with a `text/plain` mimetype will be sent into the room
to indicate the topic for the room. This overwrites any
[`m.room.topic`](/client-server-api/#mroomtopic) event in `initial_state`.
invite:
type: array
description: |-

View file

@ -34,7 +34,7 @@ properties:
topic:
type: string
description: |-
The plaintext topic of the room. Omitted if no `text/plain` mimetype
The plain text topic of the room. Omitted if no `text/plain` mimetype
exists in [`m.room.topic`](/client-server-api/#mroomtopic).
example: "All things general"
world_readable:

View file

@ -22,7 +22,7 @@ items:
The string content.
Clients SHOULD validate and sanitize the content as they do
for rich content associated with [`msgtype`](#mroommessage-msgtypes)
of [`m.room.message`](#mroommessage).
for rich content associated with [`msgtype`](/client-server-api/#mroommessage-msgtypes)
of [`m.room.message`](/client-server-api/#mroommessage).
required:
- body