Skip to content

feat(push): node SDK — notification preferences + conversation mute#20

Merged
Tsabary merged 2 commits into
mainfrom
feat/push-notifications-sdk
Jul 5, 2026
Merged

feat(push): node SDK — notification preferences + conversation mute#20
Tsabary merged 2 commits into
mainfrom
feat/push-notifications-sdk

Conversation

@Tsabary

@Tsabary Tsabary commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

push.getNotificationPreferences / push.updateNotificationPreferences and chat.muteConversation, mirroring the server routes. These are per-user operations, so — like the rest of the node-sdk surface — they take a userId (service-key acting-user override; GET via params, POST/PUT via body). Server-exact names, PUSH_EVENT_TYPES/MUTE_DURATIONS mirrored.

Part of the push-notifications feature — see the workspace plan-push-notifications.md.

🤖 Generated with Claude Code

Tsabary and others added 2 commits July 6, 2026 00:07
…unctions

Mirrors the server routes: push.getNotificationPreferences / updateNotificationPreferences
and chat.muteConversation, with server-exact names and PUSH_EVENT_TYPES/MUTE_DURATIONS.
These routes are acting-user-scoped (no service-key impersonation), so no userId param.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
muteConversation / getNotificationPreferences / updateNotificationPreferences
now take a userId (GET via params, POST/PUT via body), matching node-sdk's
existing per-user override convention, so the service-key client can act on
behalf of a named user (these routes now accept the resolveActingUserId path).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Tsabary Tsabary self-assigned this Jul 5, 2026
@Tsabary Tsabary merged commit 010d831 into main Jul 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant