Skip to main content
Version: 13.x

Notifications

Apiato notifications are just Laravel Notifications, and they function in the exact same way as Laravel notifications. However, they come with additional rules and conventions specific to Apiato.

To generate new notifications, you may use the apiato:make:notification interactive command:

php artisan apiato:make:notification

Rules​

  • All Notifications MUST extend the App\Ship\Parents\Notifications\Notification class.
  • Containers MAY or MAY NOT have one or more Notification.
  • Ship MAY contain Application general Notifications.

Folder Structure​

app
├── Containers
│   └── Section
│       └── Container
│           └── Notifications
│               ├── UserRegisteredNotification.php
│               └── ...
└── Ship
    └── Notifications
        ├── SystemFailureNotification.php
        └── ...

Code Example​

Notifications are defined exactly as you would define them in Laravel.

Database Notifications Migration​

When setting up database notifications, the usual process involves generating a migration for notifications using the php artisan notifications:table command and then running the migration.

However, Apiato already provides a migration file named xxxx_xx_xx_xxxxxx_create_notifications_table.php in the app/Ship/Migrations directory. As a result, you don't need to manually generate the migration file. You can directly run the migrations using the php artisan migrate command, and the notifications table will be created for you.