From 60b711c844f8624348d5d1dac3a625532a8e2a82 Mon Sep 17 00:00:00 2001
From: Owen Jacobson <owen@grimoire.ca>
Date: Fri, 27 Sep 2024 23:03:46 -0400
Subject: Delete expired messages out of band.

Trying to reliably do expiry mid-request was causing some anomalies:

* Creating a channel with a dup name would fail, then succeed after listing channels.

It was very hard to reason about which operations needed to trigger expiry, to fix this "correctly," so now expiry runs on every request.
---
 src/test/fixtures/filter.rs | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 src/test/fixtures/filter.rs

(limited to 'src/test/fixtures/filter.rs')

diff --git a/src/test/fixtures/filter.rs b/src/test/fixtures/filter.rs
new file mode 100644
index 0000000..8847e13
--- /dev/null
+++ b/src/test/fixtures/filter.rs
@@ -0,0 +1,9 @@
+use futures::future;
+
+use crate::events::types;
+
+pub fn messages() -> impl FnMut(&types::ResumableEvent) -> future::Ready<bool> {
+    |types::ResumableEvent(_, event)| {
+        future::ready(matches!(event.data, types::ChannelEventData::Message(_)))
+    }
+}
-- 
cgit v1.2.3