From 877d369a11ac35cf1e0cc80f45efbe8fc7dce3ef Mon Sep 17 00:00:00 2001 From: npub1223z34hd7vtwc6qj4s7flsxkj644nlre2nthu7lrrmkumhu3xddsrx9r6w <52a228d6edf316ec6812ac3c9fc0d696ab59fc7954d77e7be31eedcddf91335b@sprout-oss.stage.blox.sqprod.co> Date: Mon, 6 Jul 2026 21:35:45 -0700 Subject: [PATCH] docs(desktop): note hex64 assumption behind working-thread key split Co-authored-by: Taylor Ho Signed-off-by: Taylor Ho --- desktop/src/features/channels/ui/ChannelPane.tsx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/desktop/src/features/channels/ui/ChannelPane.tsx b/desktop/src/features/channels/ui/ChannelPane.tsx index 90ee0c54e..6866fbb1a 100644 --- a/desktop/src/features/channels/ui/ChannelPane.tsx +++ b/desktop/src/features/channels/ui/ChannelPane.tsx @@ -364,7 +364,8 @@ export const ChannelPane = React.memo(function ChannelPane({ // Thread ingress working badges: derive once per typing update, keyed on a // stable sorted string so the Set identity (and every memoized row below it) // only changes when the set of working threads changes — not on each 1s - // typing prune tick or entry-array recreation. + // typing prune tick or entry-array recreation. Splitting on "," is safe + // because thread head ids are hex64 event ids and can never contain commas. const workingThreadHeadIdKey = threadScopedBotTypingHeadIdKey(botTypingEntries); const workingThreadHeadIds = React.useMemo>(