Files
maternal-app/maternal-app/maternal-app-backend/package.json
Andrei b84271231b
Some checks failed
ParentFlow CI/CD Pipeline / Backend Tests (push) Has been cancelled
ParentFlow CI/CD Pipeline / Frontend Tests (push) Has been cancelled
ParentFlow CI/CD Pipeline / Security Scanning (push) Has been cancelled
ParentFlow CI/CD Pipeline / Build Docker Images (map[context:maternal-app/maternal-app-backend dockerfile:Dockerfile.production name:backend]) (push) Has been cancelled
ParentFlow CI/CD Pipeline / Build Docker Images (map[context:maternal-web dockerfile:Dockerfile.production name:frontend]) (push) Has been cancelled
ParentFlow CI/CD Pipeline / Deploy to Development (push) Has been cancelled
ParentFlow CI/CD Pipeline / Deploy to Production (push) Has been cancelled
CI/CD Pipeline / Lint and Test (push) Has been cancelled
CI/CD Pipeline / E2E Tests (push) Has been cancelled
CI/CD Pipeline / Build Application (push) Has been cancelled
feat: Initialize Web Push notifications infrastructure
Phase 1 of PWA push notifications implementation:
- Generated VAPID keys for Web Push API
- Created database schema (push_subscriptions, notification_queue)
- Created TypeORM entities for push management
- Installed web-push npm package
- Created PushNotifications module skeleton
- Updated implementation plan for ParentFlow architecture

Database tables:
- push_subscriptions: Store user push endpoints with VAPID keys
- notification_queue: Queue notifications for async delivery

Next steps:
- Implement services (subscription management, notification sender)
- Create REST API endpoints
- Build Service Worker and frontend integration

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-08 22:31:19 +00:00

3.9 KiB