Skip to content

Commit

Permalink
Clarify that an m.room.name event with an absent name field is no…
Browse files Browse the repository at this point in the history
…t expected behavior (#1639)

Fixes #1632

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
  • Loading branch information
zecakeh committed Sep 19, 2023
1 parent 838dec2 commit 044a787
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/1639.clarification
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarify that an `m.room.name` event with an absent `name` field is not expected behavior.
5 changes: 2 additions & 3 deletions data/event-schemas/schema/m.room.name.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,8 @@ description: |-
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.
A room with an `m.room.name` event with an absent, null, or empty
`name` field should be treated the same as a room with no `m.room.name`
event.
If a room has an `m.room.name` event with an absent, null, or empty `name`
field, it should be treated the same as a room with no `m.room.name` event.
An event of this type is automatically created when creating a room using
`/createRoom` with the `name` key.
Expand Down

0 comments on commit 044a787

Please sign in to comment.