Events

use Escalated\Laravel\Events\TicketCreated;

Event::listen(TicketCreated::class, function ($event) {
    // $event->ticket
});

Beschikbare events

• TicketCreated -- Nieuw ticket ingediend
• TicketStatusChanged -- Statusovergang
• TicketPriorityChanged -- Prioriteit bijgewerkt
• TicketAssigned -- Agent toegewezen aan ticket
• TicketUnassigned -- Agent verwijderd van ticket
• ReplyCreated -- Openbaar antwoord toegevoegd
• InternalNoteAdded -- Interne notitie van agent
• TicketUpdated -- Ticketmetadata gewijzigd
• TicketReopened -- Ticket terug naar actieve status
• DepartmentChanged -- Afdeling opnieuw toegewezen
• TagAddedToTicket -- Tag toegepast op ticket
• TagRemovedFromTicket -- Tag verwijderd van ticket
• SlaWarning -- Ticket nadert SLA-deadline
• SlaBreached -- SLA-deadline gemist
• TicketEscalated -- Ticket geescaleerd door regel
• TicketResolved -- Ticket gemarkeerd als opgelost
• TicketClosed -- Ticket gesloten

Events worden gedispatcht via ActiveSupport::Notifications. Abonneer met ActiveSupport::Notifications.subscribe("escalated.ticket_created").

Events worden gedispatcht via Django-signalen. Verbind met escalated.signals.ticket_created.connect(handler).

Events worden gedispatcht via de AdonisJS event-emitter. Abonneer met emitter.on('escalated:ticket:created', handler).

Filament gebruikt dezelfde Laravel-events van escalated-laravel. Luister ernaar op precies dezelfde manier als bij het standaard Laravel-pakket.

Events worden gedispatcht via WordPress action hooks. Gebruik add_action('escalated_ticket_created', $callback) om te luisteren naar ticketlevenscyclusevents.

Events are dispatched server-side through your backend's native event system. The Flutter package does not implement a client-side event bus.

Reactive Data

The package uses Riverpod providers that automatically refresh data when mutations occur. When a user creates a ticket, adds a reply, or changes a status, the relevant providers invalidate and re-fetch automatically.

// Ticket list stays up-to-date after creating a new ticket
final tickets = ref.watch(ticketListProvider);

// Replies refresh after posting
final replies = ref.watch(ticketRepliesProvider(ticketId));

No manual event listeners or refresh logic is needed — the provider system handles cache invalidation for you.

Note: If you need to react to server-side events (e.g., real-time agent replies), configure push notifications through your backend and handle them at the platform level.

Events are dispatched server-side through your backend's native event system. The React Native package does not implement a client-side event bus.

Reactive Data

The package uses React Query, which automatically handles cache invalidation when mutations succeed. When a user creates a ticket, adds a reply, or changes a status, the relevant queries re-fetch automatically.

import { useCreateTicket, useTickets } from '@escalated-dev/escalated-react-native';

function TicketListScreen() {
  const { data: tickets } = useTickets();
  const createTicket = useCreateTicket(); // invalidates ticket list query on success

  return (
    // Ticket list stays current — no manual refresh needed
  );
}

No manual event listeners or refresh logic is needed — React Query handles cache invalidation for you.

Note: If you need to react to server-side events (e.g., real-time agent replies), configure push notifications through your backend and handle them at the platform level.