feat: import Chinese-localized Buzz source snapshot

Signed-off-by: cls_宁波本机 <908705107@qq.com>
2026-08-13 18:34:25 +08:00
parent 61c3fa1df9
commit 9dfa06ffee
3785 changed files with 1085458 additions and 2 deletions
@@ -0,0 +1,44 @@
+import 'read_state_format.dart';
+import 'read_state_provider.dart';
+
+/// Effective read timestamp for a single message: the newest of the channel
+/// marker, the message's own `msg:` marker, and (for thread replies) the
+/// thread's `thread:` marker — the same precedence the unread badge uses via
+/// `observedUnreadEventReadAt`.
+int? effectiveMessageReadAt(
+  ReadStateState readState, {
+  required String channelId,
+  required String messageId,
+  String? threadRootId,
+}) {
+  return maxReadAt([
+    readState.effectiveTimestamp(channelId),
+    readState.effectiveTimestamp(msgContextKey(messageId)),
+    if (threadRootId != null)
+      readState.effectiveTimestamp(threadContextKey(threadRootId)),
+  ]);
+}
+
+/// Whether a message should currently show as unread in the actions menu.
+///
+/// A message-level forced unread (from this menu) wins; otherwise the
+/// timestamp precedence decides. A channel-level forced unread (from the
+/// channel tile) is deliberately not consulted: it is a channel-scoped
+/// choice, and letting it leak in here would make the message-level toggle
+/// unable to round-trip without clearing the channel-level choice.
+bool isMessageUnread(
+  ReadStateState readState, {
+  required String channelId,
+  required String messageId,
+  required int createdAt,
+  String? threadRootId,
+}) {
+  if (readState.isForcedUnread(msgContextKey(messageId))) return true;
+  final readAt = effectiveMessageReadAt(
+    readState,
+    channelId: channelId,
+    messageId: messageId,
+    threadRootId: threadRootId,
+  );
+  return readAt == null || createdAt > readAt;
+}