Fix Telegram Bad Request due to unescaped backslashes #139
Conversation
- Updated `escapeMarkdownV2` in `pkg/app/passage.go` to escape backslashes (`\` -> `\\`). - Added regression test `TestParsePassageFromHtml/Backslash_escaping` in `pkg/app/passage_test.go`. - Verified that API responses containing backslashes are now correctly formatted for Telegram.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
The application was failing to send messages to Telegram (400 Bad Request) when the Bible AI API returned text containing backslashes (e.g., pre-escaped characters). The
escapeMarkdownV2function was missing the replacement rule for\, leading to invalid MarkdownV2 syntax (e.g.,\\.where the dot was unescaped because the preceding backslash was consumed by another backslash). This change ensures backslashes are properly escaped, preventing the API error.PR created automatically by Jules for task 17994217594689462635 started by @julwrites