事件

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.