Represent channels and messages using a split "History" and "Snapshot" model.

This separates the code that figures out what happened to an entity from the code that represents it to a user, and makes it easier to compute a snapshot at a point in time (for things like bootstrap). It also makes the internal logic a bit easier to follow, since it's easier to tell whether you're working with a point in time or with the whole recorded history.

This hefty.

1 files changed, 4 insertions, 11 deletions

diff --git a/src/channel/mod.rs b/src/channel/mod.rs
index 4baa7e3..eb8200b 100644
--- a/src/channel/mod.rs
+++ b/src/channel/mod.rs
@@ -1,16 +1,9 @@
-use crate::event::Instant;
-
 pub mod app;
+pub mod event;
+mod history;
 mod id;
 pub mod repo;
 mod routes;
+mod snapshot;
 
-pub use self::{id::Id, routes::router};
-
-#[derive(Clone, Debug, Eq, PartialEq, serde::Serialize)]
-pub struct Channel {
-    pub id: Id,
-    pub name: String,
-    #[serde(skip)]
-    pub created: Instant,
-}
+pub use self::{event::Event, history::History, id::Id, routes::router, snapshot::Channel};