-
Notifications
You must be signed in to change notification settings - Fork 5
Fix bot trigger to respond only when mentioned at start of message #158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider stricter word boundary checking to avoid false positives.
The current boundary check uses
isalpha(), which means messages like"ботяра123"or"bot_health_check"would trigger the bot since digits and underscores are not alphabetic. This could lead to unintended activations.If you want strict word boundaries, consider checking for whitespace or end-of-string instead:
bot_trigger_words = ["ботяра", "bot_health"] # Remove leading/trailing whitespace and convert to lowercase cleaned_text = message_text.strip().lower() for word in bot_trigger_words: if cleaned_text.startswith(word): - # Check if it's followed by space, punctuation, or is the whole message - if len(cleaned_text) == len(word) or not cleaned_text[len(word)].isalpha(): + # Check if it's the whole message or followed by whitespace + if len(cleaned_text) == len(word) or cleaned_text[len(word)].isspace(): return True return FalseAlternatively, if you want to allow punctuation but not alphanumeric characters:
bot_trigger_words = ["ботяра", "bot_health"] # Remove leading/trailing whitespace and convert to lowercase cleaned_text = message_text.strip().lower() for word in bot_trigger_words: if cleaned_text.startswith(word): - # Check if it's followed by space, punctuation, or is the whole message - if len(cleaned_text) == len(word) or not cleaned_text[len(word)].isalpha(): + # Check if it's the whole message or followed by non-alphanumeric character + if len(cleaned_text) == len(word) or not cleaned_text[len(word)].isalnum(): return True return False📝 Committable suggestion
🤖 Prompt for AI Agents