Boot the client by consuming events.

We use the same event processing glue that the client has for keeping up with live events, which means that a significant chunk of state management code goes away entirely.

1 files changed, 4 insertions, 8 deletions

diff --git a/ui/lib/session.svelte.js b/ui/lib/session.svelte.js
index d742dbe..838401c 100644
--- a/ui/lib/session.svelte.js
+++ b/ui/lib/session.svelte.js
@@ -64,27 +64,23 @@ class Session {
     ),
   );
 
-  static boot({ user, users, channels, messages, resume_point, heartbeat }) {
+  static boot({ user, resume_point, heartbeat, events }) {
     const remote = r.State.boot({
       currentUser: user,
-      users,
-      channels,
-      messages,
       resumePoint: resume_point,
       heartbeat,
+      events,
     });
     const local = l.Channels.fromLocalStorage();
     return new Session(remote, local);
   }
 
-  reboot({ user, users, channels, messages, resume_point, heartbeat }) {
+  reboot({ user, resume_point, heartbeat, events }) {
     this.remote = r.State.boot({
       currentUser: user,
-      users,
-      channels,
-      messages,
       resumePoint: resume_point,
       heartbeat,
+      events,
     });
   }