fix: no bot username config (#15)

niracler · Jan 25, 2024 · 3ec7f55 · 3ec7f55
1 parent 04d031a
commit 3ec7f55
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/index.ts b/src/index.ts
@@ -24,7 +24,7 @@ async function handler(update: TelegramUpdate, env: Env): Promise<string | undef
     } else if (content.startsWith('/ping')) {
         return await processPingCommand(update, env)
 
-    } else if (content.includes(`@${env.TELEGRAM_BOT_USERNAME}`) && !content.startsWith('/')) {
+    } else if (env.TELEGRAM_BOT_USERNAME && content.includes(`@${env.TELEGRAM_BOT_USERNAME}`) && !content.startsWith('/')) {
         return await processLLM(update, env)
 
     } else if (content.startsWith('/sync_twitter')) {

diff --git a/wrangler.demo.toml b/wrangler.demo.toml
@@ -5,7 +5,7 @@ compatibility_flags = [ "nodejs_compat" ]
 
 [vars]
 ALLOW_USER_IDS = [ ]
-TELEGRAM_BOT_USERNAME = ''
+TELEGRAM_BOT_USERNAME = 'YOUR_BOT_USERNAME'
 
 [[d1_databases]]
 binding = "DB" # i.e. available in your Worker on env.DB