Make null m.room.name behaviour explicit

PR feedback
This commit is contained in:
Richard van der Hoff 2016-07-12 13:44:04 +01:00
parent 7b4c21fa77
commit d724b6bf75
2 changed files with 5 additions and 4 deletions

View file

@ -6,8 +6,8 @@ description: |-
considered the canonical one. This could be for display purposes or as considered the canonical one. This could be for display purposes or as
suggestion to users which alias to use to advertise the room. suggestion to users which alias to use to advertise the room.
A room with an ``m.room.canonical_alias`` event with an empty or absent A room with an ``m.room.canonical_alias`` event with an absent, null, or
``alias`` field should be treated the same as a room with no empty ``alias`` field should be treated the same as a room with no
``m.room.canonical_alias`` event. ``m.room.canonical_alias`` event.
properties: properties:
content: content:

View file

@ -7,8 +7,9 @@ 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 or empty ``name`` field A room with an ``m.room.name`` event with an absent, null, or empty
should be treated the same as a room with no ``m.room.name`` event. ``name`` field 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 An event of this type is automatically created when creating a room using
``/createRoom`` with the ``name`` key. ``/createRoom`` with the ``name`` key.