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

diff --git a/src/test/fixtures/filter.rs b/src/test/fixtures/filter.rs
index d1939a5..6e62aea 100644
--- a/src/test/fixtures/filter.rs
+++ b/src/test/fixtures/filter.rs
@@ -1,11 +1,11 @@
 use futures::future;
 
-use crate::event::types;
+use crate::event::{Event, Kind};
 
-pub fn messages() -> impl FnMut(&types::ChannelEvent) -> future::Ready<bool> {
-    |event| future::ready(matches!(event.data, types::ChannelEventData::Message(_)))
+pub fn messages() -> impl FnMut(&Event) -> future::Ready<bool> {
+    |event| future::ready(matches!(event.kind, Kind::MessageSent(_)))
 }
 
-pub fn created() -> impl FnMut(&types::ChannelEvent) -> future::Ready<bool> {
-    |event| future::ready(matches!(event.data, types::ChannelEventData::Created(_)))
+pub fn created() -> impl FnMut(&Event) -> future::Ready<bool> {
+    |event| future::ready(matches!(event.kind, Kind::ChannelCreated(_)))
 }