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, 6 insertions, 7 deletions

diff --git a/src/message/mod.rs b/src/message/mod.rs
index 9a9bf14..52d56c1 100644
--- a/src/message/mod.rs
+++ b/src/message/mod.rs
@@ -1,9 +1,8 @@
+pub mod app;
+pub mod event;
+mod history;
 mod id;
+pub mod repo;
+mod snapshot;
 
-pub use self::id::Id;
-
-#[derive(Clone, Debug, Eq, PartialEq, serde::Serialize)]
-pub struct Message {
-    pub id: Id,
-    pub body: String,
-}
+pub use self::{event::Event, history::History, id::Id, snapshot::Message};