Include historical events in the boot response.

The returned events are all events up to and including the `resume_point` in the same response. If combined with the events from `/api/events?resume_point=x`, using the same `resume_point`, the client will have a complete event history, less any events from histories that have been purged.

1 files changed, 2 insertions, 3 deletions

diff --git a/src/boot/mod.rs b/src/boot/mod.rs
index 3fc2c9e..148e87d 100644
--- a/src/boot/mod.rs
+++ b/src/boot/mod.rs
@@ -1,6 +1,4 @@
-use serde::Serialize;
-
-use crate::{channel::Channel, event::Sequence, message::Message, user::User};
+use crate::{channel::Channel, event::Event, event::Sequence, message::Message, user::User};
 
 pub mod app;
 pub mod handlers;
@@ -11,4 +9,5 @@ pub struct Snapshot {
     pub users: Vec<User>,
     pub channels: Vec<Channel>,
     pub messages: Vec<Message>,
+    pub events: Vec<Event>,
 }