mirror of
https://github.com/block/buzz.git
synced 2026-11-04 00:12:02 +00:00
ace12f7b07
A reaction created before the content-kinds history window did not render on cold-load: the pre-#1153 single-filter history fetch (all CHANNEL_EVENT_KINDS under one limit) let reactions/deletions evict older reactions from the window, so the GUI showed no reaction and re-reacting hit the relay's "duplicate: reaction already exists" guard. #1153 fixed this by fetching history with content kinds only and backfilling reactions/edits/deletions by #e reference over the loaded message ids — recency-independent. This pins that contract end-to-end: a loaded message whose only reaction is outside the history window still renders the reaction (attributed to the current user) after the #e backfill. The aux filter must carry no since/until, or an old reaction becomes unreachable again; the test asserts that too. Fails if the aux backfill regains a recency cap or history starts competing reactions against message-depth budget again. Co-authored-by: Tyler Longwell <tlongwell@block.xyz> Signed-off-by: Tyler Longwell <tlongwell@block.xyz>
Buzz
Desktop chat shell with:
- Tauri + React + TypeScript + Vite
- Tailwind CSS
- shadcn/ui-ready shared components
- Biome (lint/format/check)
- Feature-driven frontend structure
Scripts
pnpm dev- run the web frontendpnpm tauri dev- run the desktop apppnpm build- typecheck and build frontendpnpm typecheck- TypeScript checkspnpm lint- Biome lintpnpm format- Biome format (write)pnpm check- Biome check
Structure
src/shared- reusable app-wide code (ui,lib,styles)src/features- feature modules (vertical slices)src/app- top-level app composition