Fix command parsing to use the bot_command entity #20
Conversation
This file contains 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
ghost
changed the title
Telegram sends a `bot_command` entity for commands highlighted by the client, such as `/command` or `/command@botname`. This commit makes the library check whether there's a `bot_command` entity at offset 0 instead of simply checking if the message starts with `/` to ensure that formatted text beginning with a slash isn't erroneously interpreted as a command.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Telegram sends a
bot_commandentity for commands highlighted by the client, such as/commandor/command@botname. This commit makes the library check whether there's abot_commandentity at offset 0 instead of simply checking if the message starts with/to ensure that formatted text beginning with a slash isn't erroneously interpreted as a command.