Notifications

A notification is a value object first and a delivery second: you describe what happened — a title, a body, a colour, an icon, maybe actions — and a driver decides where that lands. Swapping the driver changes nothing about the calling code, which is what lets the same line be a toast in a browser and a row in a database.

Drivers

The built-in default is CurrentComponentDriver wrapping SessionDriver: it resolves the currently rendering Livewire component itself, so call-sites never have to pass $this. Both SessionDriver and LivewireEventDriver forward the full payload (title, duration, icon, actions, …), so rich toasts survive the server round-trip.

Which driver for what?

Which drivers feed the toast container? <x-wire-notifications::toast-container /> listens for a Livewire browser event, so event-dispatching drivers reach it: the default CurrentComponentDriver, SessionDriver, and LivewireEventDriver — all forward the full title/duration/icon/actions payload. FlasherDriver renders its own UI and bypasses the container; NullDriver shows nothing.

It also renders what it finds flashed, which is the same notification arriving by the other road. See Toasts that outlive the page — that is what makes an action's successRedirect(), or a create page landing on the record it just filed, announce itself at all.

Notification Builder

Notification is an immutable value object. Create via static factory, then send through NotificationManager.

use NyonCode\WireCore\Notifications\Notification;
use NyonCode\WireCore\Notifications\NotificationManager;
 
// Shorthand factories — create and send immediately
NotificationManager::success('User saved');
NotificationManager::error('Failed to delete');
 
// Build a notification, then send
$notification = Notification::success('The user was successfully updated.')
    ->title('Record Saved');
 
NotificationManager::send($notification);
 
// Full customization
$notification = Notification::make('success', 'Changes saved.')
    ->title('Done')
    ->icon('check')
    ->duration(5000)            // ms, 0 = persistent
    ->position('top-right')     // top-right, top-left, bottom-right, bottom-left
    ->extra(['link' => '/details']);
 
NotificationManager::send($notification);

Notification API

Static factories — each returns a new Notification:

Notification::make(string $type, string $message): static
Notification::success(string $message): static
Notification::error(string $message): static
Notification::warning(string $message): static
Notification::info(string $message): static

Fluent modifiers. The object is immutable, so each returns a new instance:

->title(?string $title): static
->duration(?int $ms): static      // auto-dismiss time, 0 = persistent
->persistent(bool $on = true): static   // sticky toast: duration 0, no countdown bar
->icon(?string $icon): static
->position(?string $position): static
->extra(array $data): static      // arbitrary extra data (merged)
->url(?string $url): static       // where it points — the invoice, not the notification
->to(?Model $notifiable): static  // who it is for; overrides ResolvesNotifiable
->action(NotificationAction|string $action, ?string $event = null): static
->actions(array $actions): static      // replace the action button set
->toArray(): array                // the payload only — never the recipient

Action buttons. A link survives being stored; an event needs its listener to be on the page, which a notification opened three days later has no reason to expect:

NotificationAction::make(string $label, string $event): static
NotificationAction::link(string $label, string $url): static
->payload(array $payload): static      // sent with the dispatched event
->url(?string $url): static            // go here instead of dispatching
->color(?string $color): static        // button accent; falls back to the type
->keepOpen(bool $keepOpen = true): static   // don't dismiss the toast on click

Sending. $livewire is optional — the default CurrentComponentDriver resolves the active component itself:

NotificationManager::send(Notification $n, ?NotificationDriver $driver = null, mixed $livewire = null): void
NotificationManager::sendTo(Model $notifiable, Notification $n, ...): void
NotificationManager::success(string $message, ...): void
NotificationManager::error(string $message, ...): void
NotificationManager::warning(string $message, ...): void
NotificationManager::info(string $message, ...): void

Configuration

// config/wire-core.php
return [
    'notifications' => [
        // session, livewire, flasher, database, broadcast, null — or a list
        'default' => env('WIRE_NOTIFICATIONS_DRIVER', 'session'),
    ],
];

This config value drives the container-bound NotificationDriver (resolved by the service provider for constructor/app() injection).

Driver Resolution Order

When you call NotificationManager::send() (or its shortcuts), the driver is resolved in this order:

1. Explicit driver passed to the call / component (setNotificationDriver(), the $driver argument)
2. Global default set via NotificationManager::setDefaultDriver()
3. Fallback: built-in CurrentComponentDriver wrapping SessionDriver

Note: the static NotificationManager does not read wire-core.notifications.default on its own — that config only feeds the container binding. To make the configured driver the global default for the static API, bridge it once in a service provider:

use NyonCode\WireCore\Notifications\Contracts\NotificationDriver;
use NyonCode\WireCore\Notifications\NotificationManager;
 
NotificationManager::setDefaultDriver(app(NotificationDriver::class));

In This Section

Related

• The Notifications Module — the ready-made history screen
• Actions — what usually raises one
• Colors and Icons — the vocabulary a notification speaks
• Configuration — the notification block in full