Revise Notifications API
Open
extension-breaking
type/cleanup
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
* Rename/change some database columns:
* is_read (boolean) → read_time (datetime)
* is_deleted → is_hidden
* Add `notifications_from` table (notification_id, user_id). A notification has many senders, morphs to one subject. eg, many users can like a post but we only want the user to get one notification for that (see flarum/issue-archive#318).
Contributor guide
Research direction
No files, tests, or entry points are named. Review the current notifications schema and API, then consult flarum/issue-archive#318 for the duplicate-notification context; done means the column changes and notifications_from relationship support multiple senders while producing one notification per subject.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100