From 004a4d5148a584dce21a0c85346ba818a15acb04 Mon Sep 17 00:00:00 2001 From: Kitsune Ral Date: Wed, 11 Oct 2017 02:22:19 +0900 Subject: [PATCH] Added/updated operationIds according to today's updates in the spec Signed-off-by: Alexey Rusakov --- api/client-server/list_joined_rooms.yaml | 3 ++- api/client-server/rooms.yaml | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/api/client-server/list_joined_rooms.yaml b/api/client-server/list_joined_rooms.yaml index a239871a..19ad8649 100644 --- a/api/client-server/list_joined_rooms.yaml +++ b/api/client-server/list_joined_rooms.yaml @@ -32,6 +32,7 @@ paths: summary: Lists the user's current rooms. description: |- This API returns a list of the user's current rooms. + operationId: getJoinedRooms security: - accessToken: [] responses: @@ -54,4 +55,4 @@ paths: ] } tags: - - Room membership \ No newline at end of file + - Room membership diff --git a/api/client-server/rooms.yaml b/api/client-server/rooms.yaml index 0182361e..176d9fc9 100644 --- a/api/client-server/rooms.yaml +++ b/api/client-server/rooms.yaml @@ -237,7 +237,7 @@ paths: summary: Get the m.room.member events for the room. description: Get the list of members for this room. - operationId: getRoomMembers + operationId: getMembersByRoom parameters: - in: path type: string @@ -307,6 +307,7 @@ paths: description: This API returns a map of MXIDs to member info objects for members of the room. The current user must be in the room for it to work, unless it is an Application Service in which case any of the AS's users must be in the room. This API is primarily for Application Services and should be faster to respond than ``/members`` as it can be implemented more efficiently on the server. + operationId: getJoinedMembersByRoom parameters: - in: path type: string