Skip to content

Feat/push notifications#211

Draft
IamKirbki wants to merge 12 commits intomainfrom
feat/push-notifications
Draft

Feat/push notifications#211
IamKirbki wants to merge 12 commits intomainfrom
feat/push-notifications

Conversation

@IamKirbki
Copy link
Copy Markdown
Contributor

No description provided.

…he error it was causing in GettingStarted.tsx was bothering me
- Created a new Web Push provider with full implementation in `main.go`.
- Added configuration schema for VAPID keys in the provider manifest.
- Implemented sending notifications to web browsers using the Web Push Protocol.
- Included a Makefile for building the WASM module.
- Added Quick Start guide and detailed README documentation for usage and testing.
- Updated payload structures to support Web Push targets.
- Introduced error handling for various HTTP response codes from push services.
fix(store): update VapidKeysStore to select specific columns

feat(devices): implement Scan and Value methods for DeviceCredentials; add UpsertDevice method

feat(migrations): create unique index for active devices

fix(wasm): update provider.wasm binary

feat(webpush): enhance Web Push provider to support FCM; add necessary configuration fields and logic
…ions

- Moved provider manifest and related types to a new `types` package for better organization.
- Updated the `Manifest` function to use the new types.
- Refactored the `Send` function to utilize the new `SendRequest` and `SendResponse` types.
- Enhanced Web Push notification handling with manual VAPID JWT generation and AES-128-GCM encryption.
- Improved error handling and logging throughout the code.
- Removed unused imports and redundant code for clarity and maintainability.
@jeroenrinzema jeroenrinzema marked this pull request as draft March 26, 2026 15:17
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