Eventos

use Escalated\Laravel\Events\TicketCreated;

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

Eventos disponiveis

• TicketCreated -- Novo ticket enviado
• TicketStatusChanged -- Transicao de status
• TicketPriorityChanged -- Prioridade atualizada
• TicketAssigned -- Agente atribuido ao ticket
• TicketUnassigned -- Agente removido do ticket
• ReplyCreated -- Resposta publica adicionada
• InternalNoteAdded -- Nota interna do agente
• TicketUpdated -- Metadados do ticket alterados
• TicketReopened -- Ticket movido de volta para estado ativo
• DepartmentChanged -- Departamento reatribuido
• TagAddedToTicket -- Tag aplicada ao ticket
• TagRemovedFromTicket -- Tag removida do ticket
• SlaWarning -- Ticket se aproximando do prazo de SLA
• SlaBreached -- Prazo de SLA perdido
• TicketEscalated -- Ticket escalonado por regra
• TicketResolved -- Ticket marcado como resolvido
• TicketClosed -- Ticket fechado

Eventos sao despachados via ActiveSupport::Notifications. Inscreva-se com ActiveSupport::Notifications.subscribe("escalated.ticket_created").

Eventos sao despachados via sinais do Django. Conecte com escalated.signals.ticket_created.connect(handler).

Eventos sao despachados via o emissor de eventos do AdonisJS. Inscreva-se com emitter.on('escalated:ticket:created', handler).

O Filament utiliza os mesmos eventos Laravel do escalated-laravel. Escute-os exatamente como faria com o pacote padrao do Laravel.

Eventos sao despachados via action hooks do WordPress. Use add_action('escalated_ticket_created', $callback) para escutar eventos do ciclo de vida do ticket.

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.