Feature/notification preferences 399#413
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #399
Backend (chainhook)
notification-preferences.js — MemoryNotificationPreferencesStore and PostgresNotificationPreferencesStore with full CRUD, validatePreferencesPayload, mergePreferences, and constants for channels/event types
002_add_notification_preferences.sql
— idempotent table + index migration
server.js — three new routes (GET/PUT/DELETE /api/notifications/preferences/:address), graceful shutdown cleanup, memory fallback when no DATABASE_URL
45 backend tests across unit and HTTP integration levels, all passing
Frontend
notificationPreferences.js
— localStorage persistence, defaults, isEventEnabled, isChannelEnabled helpers
NotificationPreferencesContext.jsx
— NotificationPreferencesProvider + useNotificationPreferences hook with toggleChannel, toggleEvent, setEmail, resetToDefaults, reloadFromStorage
useNotifications.js
— extended with optional preferences param; suppresses notifications when in-app channel or tip_received event is disabled
NotificationPreferences.jsx
— full settings page with accessible toggle switches, email input with validation, reset button, channel and event sections
NotificationBell.jsx
— settings gear icon in dropdown header navigates to preferences page
routes.js
— ROUTE_NOTIFICATION_PREFERENCES constant, labels, titles, and meta
App.jsx / main.jsx — provider wired in, lazy route added, nav item added
149 frontend tests across storage lib, context, component, hook integration, and bell component, all passing