v4.0.1

Fix

• Inactive corporation member notification generated URL has been fixed

v4.0.0

build(core): v4.0.0

v4.0.0 - Release Candidate 4

Enhancements

• Replace ACL system by Gates 6576b06
• Publish notifications configuration file outside package a1dde35

v4.0.0 - Release Candidate 3

Enhancements

The notification package was in need of love for a while. This has been started by a large refactor shipped with that release candidate.

Events

Most of the flow has been reviewed, based on events and non longer on a command. In the meanwhile, new commands has been designed to pull contract, killmails and character notifications more frequently, and separated from common bus.

To do so, new namespace called Observers has been introduced. You can inspire of them to upgrade your plugins if needed. They are almost simple and split in 3 stage :

1. beeing triggered by an event (created, updated, etc... or any custom event)
2. collect routes candidates based on notifications groups settings
3. dispatch notification on proper channel

Event/Driver/Routes Structures

The old Alerts namespace has been removed (replaced by Observers) and the configuration file has been revamped accordingly.

New structure is described as bellow :

• a unique key which will identify the notification
• a label property which will contain a translation token - so notification label will be translated accordingly in UI
• a list of handlers with driver name as key and handler class path as value to determine message formatter

    'MoonminingExtractionFinished' => [
        'label'   => 'notifications::alerts.moon_mining_extraction_finished',
        'handlers' => [
            'mail' => \Seat\Notifications\Notifications\Structures\Mail\MoonMiningExtractionFinished::class,
            'slack' => \Seat\Notifications\Notifications\Structures\Slack\MoonMiningExtractionFinished::class,
        ],
    ],

Notifications

All previous notifications has been converted in the new format. And a few other has been added to the collection (there still a tons of work if you want all of them, but since they are easy to built, you should be able to share them ;) )

UI

The old notification group type (formally known as char, corp & seat) has been dropped since they didn't add anything to the flow. You still have access to affiliation and be able to apply filter as you want.

Observer will handle them, or not - depending on support.

Also, the alerts list which allow you to select the kind of notification you want to received, has been updated to show you available channels for the alert itself.

Drivers

SeAT is using Laravel Notifications Channels !
If you want to add new handlers to existing notifications (or spawn new notification for different handlers), you can use them https://laravel-notification-channels.com/

pro-type: there is a Telegram driver ;)

v4.0.0 - Realase Candidate 2

4.0.0-rc2

refactor(acl): move permissions to sub-directory

v4.0.0 - Realase Candidate 1

4.0.0-rc1

refactor(core): move AbstractSeatPlugin from services to seat package…

v3.0.6

Fix

• ignore alliance from Structure Under Attack notification if only allianceID is provided (eveseat/seat#577)

v3.0.5

Enhancements

• add a notification when a character is leaving the corporation
• add a notification when a structure service is changing status
• add a notification when a moon mining extraction is available
• add a notification when a structure is running low level of fuel
• add a notification when a corporation receive a bill
• add a notification when a structure is reinforced
• add a notification when a structure is destroyed
• add a notification when a structure is under attack

Fix

• ensure entity attached to a notification (character or corporation) is properly shown in the subscription

v3.0.4

Fix

• Ensure notification related to killmail are properly dispatched using both slack and mail channel
• Ensure notification related to corporation member tracking are properly dispatched using both slack and mail channel

v3.0.3

build(core): v3.0.3