-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Improve handling of CallbackQuery in Examples #1721
Conversation
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.
Hey there. Relax, I am just a little warning for the maintainers to release directly after merging your PR, otherwise we have broken examples and people might get confused :)
Don't really need to. Nothing unreleased is used. Edit: |
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.
solid change, nothing to worry about. Good job
@@ -66,6 +66,7 @@ def start(update, context): | |||
|
|||
# If we're starting over we don't need do send a new message | |||
if context.user_data.get(START_OVER): | |||
update.callback_query.answer() |
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.
maybe we should do query = update.callbackquery in this file as well?
@Poolitzer I understood from @EchteEldin that the Keyboard wouldn't change for him because the CallbackQuery wasn't answered before editing the message. That's why I answer before editing. |
CI fails unrelated, since I only changed the examples |
CallbackQueries
even if message is editedCQs
shortcut foredit_message_text
Closes #1712