Releases: eveseat/notifications
v4.0.0
v4.0.0 - Release Candidate 4
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 :
- beeing triggered by an event (created, updated, etc... or any custom event)
- collect routes candidates based on notifications groups settings
- 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
v3.0.3
v3.0.2
Package Name | Version |
---|---|
api | 3.0.5 |
eveapi | 3.0.9 |
notifications | 3.0.2 |
services | 3.0.4 |
web | 3.0.10 |
This update primarily contains two major changes. The first relates to how table data is processed, improving the server-side handling of filters and pagination. This resulted in improved performance which could be observed in the assets views.
Secondly, a switch was introduced to view either the selected character (eg. the Main character) or all linked characters in the corresponding user group (main + all alts).
Another small, yet significant improvement includes a more reliable name resolution mechanism which should fail less.
New Features
- feat (corporation) Include main character into MemberTracking
- feat (corporation) Include main character into Corporation Mining Ledger
- feat (api) Add main_character_id to group-list
- feat (resolver): Improve resolver using local database information
- feat (profile): Provide a link to characters
- feat (dependencies): Update DataTables Dependencies for new DataTable version
- feat (contacts): Move to asynchronous loading
- feat (assets): Move to asynchronous loading
- feat (core): Provide events when a role is attached or detached from a group
- feat (contracts): Move to asynchronous loading
- feat (core): Use new migration mechanic
- feat (core): Resolve ids universe names
- feat (users): Move to asynchronous loading
- feat (killmails): Move to asynchronous loading
- feat (wallets): Move to asynchronous loading
- feat (mails): Move to asynchronous loading and show mails to be read in a pop up
- feat (transactions): Move to asynchronous loading
- feat (characters): Make the list sortable by name and turn into async
- feat (market): Update market tab and refactor partials
- feat (mails): Mailtimeline Improvement: only link existing characters and corporations
Fix
- fix (characters) Avoid the group table from characters list to throw an exception on Admin user
- fix (mining ledger): Fix loading time issue due to prices eager-load
- fix (settings): Fix GA tracking explanation dead link
- fix (mining-ledger): fix ErrorException for undefined variable character_id
- fix (assets): Add missing EVE Logo