Notification listing and read endpoints

[ayshadogo]

Description:

GET /api/v1/notifications — list and manage notifications.

Tasks:

• GET /api/v1/notifications — paginated list with filters
• PATCH /api/v1/notifications/:id/read — mark as read
• PATCH /api/v1/notifications/read-all — mark all as read
• GET /api/v1/notifications/unread-count — return count

Acceptance Criteria:

• Notifications paginated and filterable
• Mark as read updates timestamp
• Unread count accurate and cached

[guptakumarranjeet150]

Hi there,

I would love to take this on. My planned approach:

• Build out the handlers for Notification listing and read endpoints ensuring proper HTTP status codes and error propagation.
• Cover route handlers with automated endpoint integration tests.

I can start working on this right away. Please assign!

[guptakumarranjeet150]

Hey maintainers,

I can tackle Notification listing and read endpoints. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in Dfunder/stellarAid-api
• Core Implementation: Implement backend logic for Notification listing and read endpoints with strict schema validation and idempotent execution.
• Quality Assurance: Add integration test suites for standard invocations and boundary/error conditions.

I am ready to start immediately—please feel free to assign this to me!