wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify that an m.room.name event with an absent name field is not expected behavior (#1639)

Browse source 
Fixes #1632

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
Kévin Commaille 2023-09-19 16:39:07 +02:00 • committed by GitHub
parent 838dec272c
commit 044a78730e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

1
changelogs/client_server/newsfragments/1639.clarification Normal file
View file

@ -0,0 +1 @@
Clarify that an `m.room.name` event with an absent `name` field is not expected behavior.

5
data/event-schemas/schema/m.room.name.yaml
View file

@ -7,9 +7,8 @@ description: |-
is a human-friendly string designed to be displayed to the end-user. The is a human-friendly string designed to be displayed to the end-user. The
room name is not unique, as multiple rooms can have the same room name set. room name is not unique, as multiple rooms can have the same room name set.
A room with an `m.room.name` event with an absent, null, or empty If a room has an `m.room.name` event with an absent, null, or empty `name`
`name` field should be treated the same as a room with no `m.room.name` field, it should be treated the same as a room with no `m.room.name` event.
event.
An event of this type is automatically created when creating a room using An event of this type is automatically created when creating a room using
`/createRoom` with the `name` key. `/createRoom` with the `name` key.