Evenements

use Escalated\Laravel\Events\TicketCreated;

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

Evenements disponibles

• TicketCreated -- Nouveau ticket soumis
• TicketStatusChanged -- Transition de statut
• TicketPriorityChanged -- Priorite mise a jour
• TicketAssigned -- Agent assigne au ticket
• TicketUnassigned -- Agent retire du ticket
• ReplyCreated -- Reponse publique ajoutee
• InternalNoteAdded -- Note interne de l'agent
• TicketUpdated -- Metadonnees du ticket modifiees
• TicketReopened -- Ticket remis en etat actif
• DepartmentChanged -- Departement reassigne
• TagAddedToTicket -- Etiquette appliquee au ticket
• TagRemovedFromTicket -- Etiquette retiree du ticket
• SlaWarning -- Ticket approchant de l'echeance SLA
• SlaBreached -- Echeance SLA depassee
• TicketEscalated -- Ticket escalade par une regle
• TicketResolved -- Ticket marque comme resolu
• TicketClosed -- Ticket cloture

Les evenements sont emis via ActiveSupport::Notifications. Abonnez-vous avec ActiveSupport::Notifications.subscribe("escalated.ticket_created").

Les evenements sont emis via les signaux Django. Connectez-vous avec escalated.signals.ticket_created.connect(handler).

Les evenements sont emis via l'emetteur d'evenements AdonisJS. Abonnez-vous avec emitter.on('escalated:ticket:created', handler).

Filament utilise les memes evenements Laravel de escalated-laravel. Ecoutez-les exactement comme vous le feriez avec le package Laravel standard.

Les evenements sont emis via les action hooks WordPress. Utilisez add_action('escalated_ticket_created', $callback) pour ecouter les evenements du cycle de vie des tickets.

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.