From 8fe8bd6a815c3f1fa38bb9e3942cfa9ff36399db Mon Sep 17 00:00:00 2001 From: David Baker Date: Mon, 3 Oct 2016 17:33:45 +0100 Subject: [PATCH] Add is_direct to member event spec. --- api/client-server/create_room.yaml | 3 ++- event-schemas/schema/m.room.member | 3 +++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/api/client-server/create_room.yaml b/api/client-server/create_room.yaml index c4a9c8ff..ce9ab46b 100644 --- a/api/client-server/create_room.yaml +++ b/api/client-server/create_room.yaml @@ -180,7 +180,8 @@ paths: synchronised at first. Both users may subsequently choose to tag the room differently. This adds an ``is_direct`` flag to the content of any invites - sent. + sent, which will appear in the content of the `m.room.member`_ + event. responses: 200: description: Information about the newly created room. diff --git a/event-schemas/schema/m.room.member b/event-schemas/schema/m.room.member index f9aa5051..adb9a831 100644 --- a/event-schemas/schema/m.room.member +++ b/event-schemas/schema/m.room.member @@ -39,6 +39,9 @@ properties: - leave - ban type: string + is_direct: + description: Flag indicating if this room was created with the intention of being a direct chat + type: boolean third_party_invite: properties: display_name: