github/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-08 11:21:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix Telegram token resolution for non-normalized accountId keys

Browse Source
This commit is contained in:
jasonsschin
2026-01-31 11:48:38 +11:00
committed by Ayaan Zaidi
parent c0a6e675a3
commit e913de0720
2 changed files with 35 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
src/telegram/token.ts
View File

@@ -22,10 +22,23 @@ export function resolveTelegramToken(
): TelegramTokenResolution {
const accountId = normalizeAccountId(opts.accountId);
const telegramCfg = cfg?.channels?.telegram;
const accountCfg =
accountId !== DEFAULT_ACCOUNT_ID
? telegramCfg?.accounts?.[accountId]
: telegramCfg?.accounts?.[DEFAULT_ACCOUNT_ID];
// Account IDs are normalized for routing (e.g. lowercased). Config keys may not
// be normalized, so resolve per-account config by matching normalized IDs.
const resolveAccountCfg = (id: string) => {
const accounts = telegramCfg?.accounts;
if (!accounts || typeof accounts !== "object") return undefined;
// Direct hit (already normalized key)
const direct = (accounts as any)[id];
if (direct) return direct as any;
// Fallback: match by normalized key
const matchKey = Object.keys(accounts).find((k) => normalizeAccountId(k) === id);
return matchKey ? ((accounts as any)[matchKey] as any) : undefined;
};
const accountCfg = resolveAccountCfg(
accountId !== DEFAULT_ACCOUNT_ID ? accountId : DEFAULT_ACCOUNT_ID,
);
const accountTokenFile = accountCfg?.tokenFile?.trim();
if (accountTokenFile) {
if (!fs.existsSync(accountTokenFile)) {