이벤트

use Escalated\Laravel\Events\TicketCreated;

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

사용 가능한 이벤트

• TicketCreated -- 새 티켓이 제출됨
• TicketStatusChanged -- 상태 전환
• TicketPriorityChanged -- 우선순위 업데이트
• TicketAssigned -- 에이전트가 티켓에 할당됨
• TicketUnassigned -- 에이전트가 티켓에서 해제됨
• ReplyCreated -- 공개 답변 추가
• InternalNoteAdded -- 에이전트 내부 메모
• TicketUpdated -- 티켓 메타데이터 변경
• TicketReopened -- 티켓이 활성 상태로 복원됨
• DepartmentChanged -- 부서 재할당
• TagAddedToTicket -- 티켓에 태그 적용
• TagRemovedFromTicket -- 티켓에서 태그 제거
• SlaWarning -- 티켓이 SLA 마감에 근접
• SlaBreached -- SLA 마감 초과
• TicketEscalated -- 규칙에 의해 티켓이 에스컬레이션됨
• TicketResolved -- 티켓이 해결됨으로 표시됨
• TicketClosed -- 티켓이 종료됨

이벤트는 ActiveSupport::Notifications를 통해 디스패치됩니다. ActiveSupport::Notifications.subscribe("escalated.ticket_created")로 구독하세요.

이벤트는 Django 시그널을 통해 디스패치됩니다. escalated.signals.ticket_created.connect(handler)로 연결하세요.

이벤트는 AdonisJS 이벤트 이미터를 통해 디스패치됩니다. emitter.on('escalated:ticket:created', handler)로 구독하세요.

Filament는 escalated-laravel과 동일한 Laravel 이벤트를 사용합니다. 표준 Laravel 패키지와 정확히 같은 방법으로 리슨할 수 있습니다.

이벤트는 WordPress 액션 훅을 통해 디스패치됩니다. add_action('escalated_ticket_created', $callback)를 사용하여 티켓 라이프사이클 이벤트를 리슨하세요.

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.