Flatten nested `channel` and `message` structs in events and API responses.

This structure didn't accomplish anything and made certain refactorings harder.

1 files changed, 5 insertions, 5 deletions

diff --git a/hi-ui/src/apiServer.js b/hi-ui/src/apiServer.js
index f4a89a4..ec94e82 100644
--- a/hi-ui/src/apiServer.js
+++ b/hi-ui/src/apiServer.js
@@ -56,18 +56,18 @@ export function subscribeToEvents(resume_point) {
 
     switch (data.type) {
       case 'created':
-        channelsList.update((value) => value.addChannel(data.channel))
+        channelsList.update((value) => value.addChannel(data.id, data.name))
         break;
       case 'message':
         messages.update((value) => value.addMessage(data));
         break;
       case 'message_deleted':
-        messages.update((value) => value.deleteMessage(data.channel.id, data.message));
+        messages.update((value) => value.deleteMessage(data.channel.id, data.id));
         break;
       case 'deleted':
-        activeChannel.update((value) => value.deleteChannel(data.channel));
-        channelsList.update((value) => value.deleteChannel(data.channel));
-        messages.update((value) => value.deleteChannel(data.channel));
+        activeChannel.update((value) => value.deleteChannel(data.id));
+        channelsList.update((value) => value.deleteChannel(data.id));
+        messages.update((value) => value.deleteChannel(data.id));
         break;
       default:
         break;