Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
Adds new WebSocket event subscriptions to OneKey. Use when implementing new socket events, handling server push messages, or adding real-time data subscriptions. Socket, WebSocket, event, subscription, push, real-time.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill documents how to add new WebSocket event subscriptions in the OneKey app.
WebSocket events enable real-time server-to-client communication. The pattern involves:
EAppSocketEventNames enumPushProviderWebSocket| Purpose | Location |
|---|---|
| Event names & payload types | packages/shared/types/socket.ts |
| WebSocket event handlers | packages/kit-bg/src/services/ServiceNotification/PushProvider/PushProviderWebSocket.ts |
Add the new event name to EAppSocketEventNames in packages/shared/types/socket.ts:
export enum EAppSocketEventNames {
notification = 'notification',
ping = 'ping',
pong = 'pong',
ack = 'ack',
market = 'market',
primeConfigChanged = 'CONFIG_CHANGE',
// ... existing events
myNewEvent = 'MY_NEW_EVENT', // Add your new event
}
Convention: Use camelCase for the enum key, SCREAMING_SNAKE_CASE for the string value.
Add the payload interface in packages/shared/types/socket.ts:
export interface IMyNewEventPayload {
msgId: string; // Required for acknowledgment
// Add other fields as needed
someData?: string;
someNumber?: number;
}
Important: Always include msgId: string for message acknowledgment.
In packages/kit-bg/src/services/ServiceNotification/PushProvider/PushProviderWebSocket.ts:
import type {
// ... existing imports
IMyNewEventPayload,
} from '@onekeyhq/shared/types/socket';
initWebSocket() method:this.socket.on(EAppSocketEventNames.myNewEvent, (payload: IMyNewEventPayload) => {
// 1. Acknowledge receipt (required for most events)
void this.backgroundApi.serviceNotification.ackNotificationMessage({
msgId: payload.msgId,
action: ENotificationPushMessageAckAction.arrived,
});
// 2. Handle the event (call appropriate service method)
void this.backgroundApi.someService.handleMyNewEvent(payload);
});
Here's a real example from the codebase:
export enum EAppSocketEventNames {
// ... other events
userInfoUpdated = 'USER_INFO_UPDATED',
}
export interface IUserInfoUpdatedPayload {
msgId: string;
}
this.socket.on(EAppSocketEventNames.userInfoUpdated, (payload: IUserInfoUpdatedPayload) => {
void this.backgroundApi.serviceNotification.ackNotificationMessage({
msgId: payload.msgId,
action: ENotificationPushMessageAckAction.arrived,
});
void this.backgroundApi.servicePrime.apiFetchPrimeUserInfo();
});
this.socket.on(EAppSocketEventNames.myEvent, (payload: IMyPayload) => {
void this.backgroundApi.serviceNotification.ackNotificationMessage({
msgId: payload.msgId,
action: ENotificationPushMessageAckAction.arrived,
});
void this.backgroundApi.someService.doSomething();
});
this.socket.on(EAppSocketEventNames.myEvent, (payload: IMyPayload) => {
defaultLogger.notification.websocket.consoleLog(
'WebSocket received myEvent:',
payload,
);
void this.backgroundApi.serviceNotification.ackNotificationMessage({
msgId: payload.msgId,
action: ENotificationPushMessageAckAction.arrived,
});
void this.backgroundApi.someService.doSomething(payload);
});
this.socket.on(EAppSocketEventNames.myEvent, async (payload: IMyPayload) => {
if (!payload?.requiredField) {
console.error('myEvent ERROR: requiredField is missing', payload);
return;
}
void this.backgroundApi.serviceNotification.ackNotificationMessage({
msgId: payload.msgId,
action: ENotificationPushMessageAckAction.arrived,
});
await this.backgroundApi.someService.doSomething(payload);
});
this.socket.on(EAppSocketEventNames.myEvent, (payload: IMyPayload) => {
void this.backgroundApi.serviceNotification.ackNotificationMessage({
msgId: payload.msgId,
action: ENotificationPushMessageAckAction.arrived,
});
appEventBus.emit(EAppEventBusNames.MyEventReceived, payload);
});
You MUST acknowledge messages via serviceNotification.ackNotificationMessage. If you don't acknowledge the msgId, the server will assume the message was not delivered and will retry sending it repeatedly.
void this.backgroundApi.serviceNotification.ackNotificationMessage({
msgId: payload.msgId,
action: ENotificationPushMessageAckAction.arrived,
});
This should be called as early as possible in your event handler to prevent duplicate message delivery.
Available actions in ENotificationPushMessageAckAction:
arrived - Message was received (use this for most cases)clicked - User clicked the notificationEAppSocketEventNames enummsgId: stringPushProviderWebSocket.tsinitWebSocket() methodackNotificationMessage (required to prevent server retries)まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
日本語の概要は準備中です。原文の説明を表示しています。
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
日本語の概要は準備中です。原文の説明を表示しています。
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
日本語の概要は準備中です。原文の説明を表示しています。