Refactor TelegramChannel to handle additional notification types
This commit is contained in:
parent
4667f96b40
commit
aae81313a6
1 changed files with 2 additions and 0 deletions
|
|
@ -22,6 +22,8 @@ public function send($notifiable, $notification): void
|
|||
$topicId = data_get($notifiable, 'telegram_notifications_test_message_thread_id');
|
||||
break;
|
||||
case 'App\Notifications\Application\StatusChanged':
|
||||
case 'App\Notifications\Container\ContainerRestarted':
|
||||
case 'App\Notifications\Container\ContainerStopped':
|
||||
$topicId = data_get($notifiable, 'telegram_notifications_status_changes_message_thread_id');
|
||||
break;
|
||||
case 'App\Notifications\Application\DeploymentSuccess':
|
||||
|
|
|
|||
Loading…
Reference in a new issue