adjust to naming convention

Why are there different types for the seeminly same purpose on front and
backend?

Author: Septias

backend/instance.ts

@@ -136,7 +136,7 @@ export class Instances {
           instance.webXdc.connectRealtime((data) => {
             return broadcast(
               wss,
-              JSON.stringify({ type: "sendRealtime", data }),
+              JSON.stringify({ type: "realtime", data }),
             );
           });
         } else if (isSetUpdateListenerMessage(parsed)) {

backend/message.ts

@@ -193,7 +193,7 @@ class Processor implements IProcessor {
 
   distributeRealtime(instanceId: string, data: Uint8Array) {
     this.onMessage({
-      type: "sendRealtime",
+      type: "realtime-sent",
       instanceId: instanceId,
       instanceColor: getColorForId(instanceId),
       data,

sim/create.ts

@@ -260,7 +260,7 @@ export function createWebXdc(
       );
       transport.onConnect(() => {
         realtime!.sendHook = (data) => {
-          transport.send({ type: "realtime", data } as RealtimeMessage);
+          transport.send({ type: "sendRealtime", data });
           log("send realtime", { data });
         };
       });

types/message.ts

@@ -16,8 +16,8 @@ export type UpdateMessage =
 
 export type Message =
   | UpdateMessage
-  | ({ type: "sendRealtime"; data: Uint8Array } & InstanceMessage)
   | ({ type: "clear" } & InstanceMessage)
   | ({ type: "connect" } & InstanceMessage)
   | ({ type: "connect-realtime" } & InstanceMessage)
+  | ({ type: "realtime-sent"; data: Uint8Array } & InstanceMessage)
   | ({ type: "realtime-received"; data: Uint8Array } & InstanceMessage);