feat/dm-mute #60
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/dm-mute"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Unify DM and room mute handling by dropping the special-case `kind == "dm"` bypass in `push::dispatch` and the WS `Mentioned` arm. Both now consult `room_mute_mode` uniformly, so a muted DM room suppresses push and WS notification events the same way a muted channel does. On the UI side, extract the DM header into a standalone `dm_header.html` partial backed by `DmHeaderFragment`, add a Mute checkbox that POSTs to `/dm/{peer_id}/mute` and swaps the header `outerHTML` in place, and pass the current `mute_mode` from the page handler into the template. The sidebar now reads `peer.mute_mode` instead of hardcoding `"none"`, so muted peers render in a greyed link style. Add a `DmMuteChanged` WS event that triggers a sidebar OOB re-render across the muter's open tabs, and register it in `render_event` as a no-op fallback. Update tests: rename the old bypass test to confirm DM events are now dropped when muted, and add a complementary test confirming they fire when unmuted..into()calls on Protocol errors 175b4ee88fjust --listin Claude Code permissions 9fd5fd5b01