-
Notifications
You must be signed in to change notification settings - Fork 6k
API 6.6 #3584
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
API 6.6 #3584
Conversation
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
|
@marcosdodo please stop spamming, if you continue to do so, you'll be banned |
I had implemented the renaming for `StickerSet only`
other tests are probably failing not due to me having changed something...
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! Looks like you edited README.rst or README_RAW.rst. I'm just a friendly reminder to apply relevant changes to both of those files :)
* add aliases to support calls to old methods * issue deprecation warning if an old method is called * WEIRD ERROR in `test_sticker_set_to_dict()` (see my TODO note there)
* add aliases to support calls to old methods * issue deprecation warning if an old method is called * WEIRD ERROR in `test_sticker_set_to_dict()` (see my TODO note there)
the method will be removed anyway, no need to add new parameter to it.
the tests were passing because Bot API still supports the old method
harshil21
left a comment
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.
phew! Huge update with lots of changes (mostly boilerplate 😞)..
I wonder if we could've gotten away with the renaming by just overriding __(set/get)attr__ in TelegramObject to detect the usage of deprecated parameters
Co-authored-by: Harshil <37377066+harshil21@users.noreply.github.com>
This reverts commit b2cd7c2.
Poolitzer
left a comment
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.
LGTM
Checklist for PRs
.. versionadded:: version,.. versionchanged:: versionor.. deprecated:: versionto the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)AUTHORS.rst(optional)__all__sToDo
InputStickermust be tested with local mode @harshil21InputSticker- Toattach://or notatttach://tdlib/telegram-bot-api#375 : Double check ifInputStickershould be uploaded viaattach://If the PR contains API changes (otherwise, you can delete this passage)
New classes:
self._id_attrsand corresponding documentation__init__acceptsapi_kwargsas kw-onlyAdded new shortcuts:
Chat&Userfor all methods that acceptchat/user_idMessagefor all methods that acceptchat_idandmessage_idMessageshortcuts: Addedquoteargument if methods acceptsreply_to_message_idCallbackQueryfor all methods that accept eitherchat_idandmessage_idorinline_message_idIf relevant:
telegram.constantsand shortcuts to them as class variablesMessage.effective_attachmentConversationHandler_extbot.pybot_methods.rstREADME.rstandREADME_RAW.rst(including the badge), as well astelegram.constants.BOT_API_VERSION_INFOtg.ext.Botfor new methods that either accept areply_markupin some form or have a return type that is/containstelegram.Message