Replace inbox_listeners.go with a subscriber-driven notification system: - Add issue_subscriber table with auto-subscribe on create/assign/comment - New subscriber_listeners.go: maintains subscriber data on domain events - New notification_listeners.go: notifySubscribers (fanout to all subscribers minus actor) and notifyDirect (targeted, punches through unsubscribe) - Subscriber API: list/subscribe/unsubscribe endpoints - Frontend: subscribers section in issue detail sidebar with real-time sync - Frontend: inbox notification grouping by (issue_id, type, actor_id) - Remove createInboxForIssueCreator from task.go (unified through event bus) - 21 new Go tests, all passing Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
11 lines
569 B
SQL
11 lines
569 B
SQL
-- Issue subscribers: tracks who is subscribed to notifications for an issue
|
|
CREATE TABLE issue_subscriber (
|
|
issue_id UUID NOT NULL REFERENCES issue(id) ON DELETE CASCADE,
|
|
user_type TEXT NOT NULL CHECK (user_type IN ('member', 'agent')),
|
|
user_id UUID NOT NULL,
|
|
reason TEXT NOT NULL CHECK (reason IN ('creator', 'assignee', 'commenter', 'mentioned', 'manual')),
|
|
created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
|
|
PRIMARY KEY (issue_id, user_type, user_id)
|
|
);
|
|
|
|
CREATE INDEX idx_issue_subscriber_user ON issue_subscriber(user_type, user_id);
|