Skip to content

Notification anchor service#212

Merged
ezraripps merged 5 commits intomainfrom
feature/add-notification-anchor
Mar 17, 2026
Merged

Notification anchor service#212
ezraripps merged 5 commits intomainfrom
feature/add-notification-anchor

Conversation

@ezraripps
Copy link
Copy Markdown
Member

@ezraripps ezraripps commented Mar 10, 2026

This PR adds support for notification anchors,

users can register subscriptions and targets, then receive notifications when those subscriptions trigger

@ezraripps ezraripps self-assigned this Mar 10, 2026
@rkeene rkeene added this to the v0.0.43 milestone Mar 11, 2026
@rkeene rkeene removed this from the v0.0.43 milestone Mar 13, 2026
@ezraripps ezraripps marked this pull request as ready for review March 16, 2026 16:08
@ezraripps ezraripps changed the title wip: notification anchor service Notification anchor service Mar 16, 2026
@rkeene rkeene added this to the v0.0.44 milestone Mar 16, 2026
@rkeene rkeene requested review from Copilot and rkeene March 17, 2026 17:17
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new notification anchor service to the codebase, including the HTTP server implementation, a resolver-integrated client, shared request/response types, and tests to validate the basic flows.

Changes:

  • Added KeetaNetNotificationAnchorHTTPServer with routes to register/list/delete targets and create/list/delete subscriptions.
  • Added a resolver-driven KeetaNotificationAnchorClient/Provider for calling notification providers discovered via service metadata.
  • Introduced shared notification types + typia-generated runtime assertions, plus Vitest coverage for server and client behavior.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
src/services/notification/server.ts New notification anchor HTTP server with signed request verification and service metadata exposure
src/services/notification/server.test.ts Server tests for target/subscription lifecycle + invalid signature rejection
src/services/notification/common.ts Shared API types, signable payload builders, and notification-specific error type
src/services/notification/common.generated.ts typia-generated asserts/is helpers for notification API JSON
src/services/notification/client.ts Resolver-integrated notification client/provider with signing + response validation
src/services/notification/client.test.ts Client integration test wiring server metadata into Resolver and exercising flows
src/lib/resolver.ts Adds notification service metadata + lookup criteria and filtering support
src/client/index.ts Exposes Notification.Client and config types via the top-level client namespace

Comment thread src/services/notification/server.ts
Comment thread src/services/notification/common.ts Outdated
Comment thread src/services/notification/common.ts
Comment thread src/services/notification/common.ts Outdated
Comment thread src/services/notification/common.ts Outdated
@sonarqubecloud
Copy link
Copy Markdown

@ezraripps ezraripps merged commit c679395 into main Mar 17, 2026
2 checks passed
@ezraripps ezraripps deleted the feature/add-notification-anchor branch March 17, 2026 18:09
rkeene added a commit that referenced this pull request Mar 17, 2026
This is KeetaNet Anchor v0.0.44 which has the following changes:
- c679395 Notification anchor service
(#212)
- 1e7b86a Fix imports from KeetaNet
Node (#221)
- dec5d8a Fix GitHub Release notes
(#219)
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.

3 participants