Releases: teamnovu/laravel-notification-log
Releases · teamnovu/laravel-notification-log
v2.0.0
Full Changelog: v1.3.3...v2.0.0
v1.3.3
v1.3.2
Full Changelog: v1.3.1...v1.3.2
v1.3.1
Full Changelog: v1.3.0...v1.3.1
v1.3.0
Breaking Change
You now need to apply the following Interface and Trait so a Notification can be logged:
use Teamnovu\LaravelNotificationLog\Concerns\LogNotification;
use Teamnovu\LaravelNotificationLog\Contracts\ShouldLogNotification;
class DummyNotification extends Notification implements ShouldLogNotification
{
use LogNotification;
// ...
}
Full Changelog: v1.2.0...v1.3.0
v1.2.0
What's Changed
- Add way to resolve messages of notifications for several Notification Channels like sms, telegram, webpush and so on... by @okaufmann in #1
Breaking Changes
You need to update some Database Columns with the following migration.
Schema::table('sent_notification_logs', function (Blueprint $table) {
$table->text('response')->nullable()->change();
$table->after('response', function (Blueprint $table) {
$table->json('message')->nullable();
$table->string('status')->nullable();
});
});
New Contributors
- @okaufmann made their first contribution in #1
Full Changelog: v1.1.4...v1.2.0
v1.1.4
Full Changelog: v1.1.3...v1.1.4
v1.1.3
Full Changelog: v1.1.2...v1.1.3
v1.1.2
Full Changelog: v1.1.1...v1.1.2
v1.1.1
Full Changelog: v1.1.0...v1.1.1