akash-network / akash-network/console
API for providers to list notifications
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
The provider-console needs the ability to fetch notifications that were created via the API or other system processes. This issue adds a read/query capability so providers can view their notifications within the UI.
Together with the POST /v1/notifications endpoint (see API for Providers to create notifications), this completes the initial notification lifecycle for providers.
Goals
- Add GET /v1/notifications endpoint for listing and querying provider notifications.
- Add GET /v1/notifications/{id} for fetching a single notification by ID.
- Enforce provider authentication (providers can only see their own notifications).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing notification API and the POST /v1/notifications work referenced in the issue. Trace the provider authentication and notification storage, then consider the work complete when both GET endpoints support provider-scoped listing and single-notification lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100