ClientChan: does need a user array after all

thelounge · Apr 7, 2024 · 6f274c0 · 6f274c0
1 parent e91fecb
commit 6f274c0
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 0 deletions.
diff --git a/client/js/chan.ts b/client/js/chan.ts
@@ -20,6 +20,7 @@ export function toClientChan(shared: SharedNetworkChan): ClientChan {
 		inputHistoryPosition: 0,
 		historyLoading: false,
 		scrolledToBottom: true,
+		users: [],
 		usersOutdated: shared.type === "channel" ? true : false,
 		moreHistoryAvailable: shared.totalMessages > shared.messages.length,
 		inputHistory: history,

diff --git a/client/js/socket-events/network.ts b/client/js/socket-events/network.ts
@@ -39,6 +39,7 @@ socket.on("network:status", function (data) {
 
 	if (!data.connected) {
 		network.channels.forEach((channel) => {
+			channel.users = []; // TODO: untangle this
 			channel.state = ChanState.PARTED;
 		});
 	}

diff --git a/client/js/types.d.ts b/client/js/types.d.ts
@@ -34,6 +34,8 @@ type ClientChan = Omit<SharedChan, "messages"> & {
 	historyLoading: boolean;
 	scrolledToBottom: boolean;
 	usersOutdated: boolean;
+
+	users: ClientUser[];
 };
 
 type InitClientChan = ClientChan & {