From 9cdbd63661739ed0d4149875c97f0654c786be13 Mon Sep 17 00:00:00 2001 From: Duncan Date: Thu, 13 Aug 2026 18:15:24 -0400 Subject: [PATCH] docs(desktop): correct stale post-subscribe refetch comment The enforceMessageWindowBounds doc referenced shouldRefreshChannelWindowAfterSubscribe, a seam #5662 removed when it made the post-subscribe refetch unconditional. Describe the current behavior instead. Co-authored-by: Will Pfleger Signed-off-by: Will Pfleger --- desktop/src/features/messages/lib/boundMessageWindows.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/desktop/src/features/messages/lib/boundMessageWindows.ts b/desktop/src/features/messages/lib/boundMessageWindows.ts index 15e13e93cc..1e6d69fc1b 100644 --- a/desktop/src/features/messages/lib/boundMessageWindows.ts +++ b/desktop/src/features/messages/lib/boundMessageWindows.ts @@ -98,7 +98,7 @@ function foldUnits(queries: ClassifiedQuery[]): Map { * queries. Channels and threads are bounded independently. * * Removal (not invalidation) is deliberate: a removed key reads back as absent, - * so `shouldRefreshChannelWindowAfterSubscribe` re-fetches fresh on revisit. + * so a revisit re-fetches fresh via the unconditional post-subscribe refetch. * Deferred background writers (reaction/aux hydration, ancestor loads, mutation * success handlers) fire after their own promise settles with no pin, so each * commits through `updateRetainedMessageUnit`; bumping the evicted unit's