Normalize text extraction from WhatsApp event message - #29
Conversation
- Centralized text extraction logic in `normalizeBaileysEvent`. - Added support for more message types: `buttonsResponseMessage`, `listResponseMessage`, and `templateButtonReplyMessage`. - Included `pushName` in the normalized event object. - Fixed `userId` derivation to handle both group and private messages correctly. - Simplified `whatsappHook.js` to use the normalized `event.message.text` and `pushName`. Co-authored-by: Rukafuu <111822334+Rukafuu@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
This PR improves the robustness and consistency of WhatsApp message processing by centralizing and expanding the text extraction logic during event normalization.
Key changes:
normalizeBaileysEventnow correctly extracts text from button responses, list responses, and template button replies, in addition to standard conversations and media captions.pushName.userIdderivation to correctly usemsg.key.participantfor group messages andmsg.key.remoteJidfor private messages.whatsappHook.jsto rely on the unifiedevent.message.textfield, removing redundant extraction logic and improving maintainability.Verified with a test suite covering various Baileys message structures.
PR created automatically by Jules for task 4684189740669408615 started by @Rukafuu