What?

Create a minimum viable product of the notification plugin.

Why?

There is still a lot to learn, but we need a minimally functional system to explore the possiblities.

How?

Combines PRs:

• feature(mvp): Stage 4 add item and collection schemas to rest api #178
• feature(mvp): Stage 4 - add activator and uninstaller #298
• feature: add basic Logger class #204
• feature: add seed channels command #214
• feature(mvp): Stage 3 - add channel registry #291
• ci: remove php 7.2 add 8.1 and 8.2 #255
• build: update composer packages #256

Necessary functionality for MVP*

• Activate
• Uninstall
• Classes
  • Channel
  • Channel_Registry
  • Message
  • Message_Factory
  • Notice
  • Notice_Factory
  • Subscription
  • Subscription_Factory
• Database
  • Messages table
  • Queue table
  • Subscriptions table
  • Message_Repository
  • Notice_Repository (the queue table)
  • Subscription_Repository
• REST API
  • Notification_Controller wp-notifications/v1/notifications
    • GET /notifications/
    • GET /notifications/{id}
    • POST /notifications/{id}
    • PUT /notifications /{id}
    • DELETE /notifications /{id}
  • Subscription_Controller wp-notifications/v1/subscriptions
    • GET /subscriptions/
    • GET /subscriptions/{id}
    • POST /subscriptions/{id}
    • PUT /subscriptions /{id}
    • DELETE /subscriptions /{id}
• CLI Command
  • Seed users
  • Seed subscriptions
  • Seed notification messages
  • List registered channels
  • List user's notifications
  • List user's subscriptions

• Only a rough outline right now, and heavily concentrated on the backend.