Eventos

use Escalated\Laravel\Events\TicketCreated;

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

Eventos disponibles

• TicketCreated -- Nuevo ticket enviado
• TicketStatusChanged -- Transicion de estado
• TicketPriorityChanged -- Prioridad actualizada
• TicketAssigned -- Agente asignado al ticket
• TicketUnassigned -- Agente removido del ticket
• ReplyCreated -- Respuesta publica agregada
• InternalNoteAdded -- Nota interna del agente
• TicketUpdated -- Metadatos del ticket modificados
• TicketReopened -- Ticket devuelto a estado activo
• DepartmentChanged -- Departamento reasignado
• TagAddedToTicket -- Etiqueta aplicada al ticket
• TagRemovedFromTicket -- Etiqueta removida del ticket
• SlaWarning -- Ticket acercandose al limite de SLA
• SlaBreached -- Limite de SLA incumplido
• TicketEscalated -- Ticket escalado por regla
• TicketResolved -- Ticket marcado como resuelto
• TicketClosed -- Ticket cerrado

Los eventos se despachan mediante ActiveSupport::Notifications. Suscribete con ActiveSupport::Notifications.subscribe("escalated.ticket_created").

Los eventos se despachan mediante senales de Django. Conecta con escalated.signals.ticket_created.connect(handler).

Los eventos se despachan mediante el emisor de eventos de AdonisJS. Suscribete con emitter.on('escalated:ticket:created', handler).

Filament utiliza los mismos eventos de Laravel de escalated-laravel. Escuchalos exactamente como lo harias con el paquete estandar de Laravel.

Los eventos se despachan mediante action hooks de WordPress. Usa add_action('escalated_ticket_created', $callback) para escuchar los eventos del ciclo de vida de 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.