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, 9 deletions

diff --git a/src/test/fixtures/message.rs b/src/test/fixtures/message.rs
index fd50887..381b10b 100644
--- a/src/test/fixtures/message.rs
+++ b/src/test/fixtures/message.rs
@@ -1,17 +1,12 @@
 use faker_rand::lorem::Paragraphs;
 
-use crate::{app::App, channel::Channel, clock::RequestedAt, event::types, login::Login};
+use crate::{app::App, channel::Channel, clock::RequestedAt, login::Login, message::Message};
 
-pub async fn send(
-    app: &App,
-    login: &Login,
-    channel: &Channel,
-    sent_at: &RequestedAt,
-) -> types::ChannelEvent {
+pub async fn send(app: &App, channel: &Channel, login: &Login, sent_at: &RequestedAt) -> Message {
     let body = propose();
 
-    app.events()
-        .send(login, &channel.id, &body, sent_at)
+    app.messages()
+        .send(&channel.id, login, sent_at, &body)
         .await
         .expect("should succeed if the channel exists")
 }