romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(web): pass accountId in WhatsApp provider activity tracking

Browse Source 
Recent changes added recordProviderActivity calls with accountId, but
the type definition and usage didn't include accountId in ActiveWebSendOptions.
This fix adds the optional accountId field and uses optional chaining
when accessing it to handle cases where options is undefined.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Tu Nombre Real 2026-01-09 00:08:36 +01:00 committed by Peter Steinberger
parent 1a3d0bace2
commit 4491e9c8d5
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/web/active-listener.ts
View File

@ -3,6 +3,7 @@ import { DEFAULT_ACCOUNT_ID } from "../routing/session-key.js";
export type ActiveWebSendOptions = {
gifPlayback?: boolean;
accountId?: string;
};
export type ActiveWebListener = {

4
src/web/inbound.ts
View File

@ -587,7 +587,7 @@ export async function monitorWebInbox(options: {
const result = await sock.sendMessage(jid, payload);
recordProviderActivity({
provider: "whatsapp",
accountId: options.accountId,
accountId: options?.accountId,
direction: "outbound",
});
return { messageId: result?.key?.id ?? "unknown" };
@ -610,7 +610,7 @@ export async function monitorWebInbox(options: {
});
recordProviderActivity({
provider: "whatsapp",
accountId: options.accountId,
accountId: options?.accountId,
direction: "outbound",
});
return { messageId: result?.key?.id ?? "unknown" };