From b744dbaab7d7feb3008f144a369d7f7cb4309eea Mon Sep 17 00:00:00 2001
From: lukebarnard <luke.barnard99@gmail.com>
Date: Tue, 6 Feb 2018 11:56:55 +0000
Subject: [PATCH] Handle setting a newTag without metaData

metaData is actually the request body for the PUT that adds the tag
so we need to send {} for e.g. m.lowpriority, which is not manually
ordered.
---
 src/actions/RoomListActions.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/actions/RoomListActions.js b/src/actions/RoomListActions.js
index 3e0ea53a33..5802dbcaed 100644
--- a/src/actions/RoomListActions.js
+++ b/src/actions/RoomListActions.js
@@ -114,7 +114,7 @@ RoomListActions.tagRoom = function(matrixClient, room, oldTag, newTag, oldIndex,
             (hasChangedSubLists || metaData)
         ) {
             // Optimistic update of what will happen to the room tags
-            room.tags[newTag] = metaData;
+            room.tags[newTag] = metaData || {};
 
             const promiseToAdd = matrixClient.setRoomTag(roomId, newTag, metaData).catch(function(err) {
                 const ErrorDialog = sdk.getComponent("dialogs.ErrorDialog");