Conversation
Also fix a message entity fixture
Bibo-Joshi
left a comment
There was a problem hiding this comment.
Thanks for the quick PR!
- which fixture did you fix ragarding message entities?
- I guess
test_botis yet to be adapted? :D
Thanks for the quick review!
See
I'm not sure what more to change in it, i'll see |
ah, you mean
well, currently codecov complains about all the |
Bibo-Joshi
left a comment
There was a problem hiding this comment.
Nice! Apart from nitpicking, I guess it's ready, though I'd like for @Poolitzer to have a look as well.
just double checking: are you both comfortable with postponing Defaults.protect_content to v14? If you prefer to include it directly, we can do that.
|
pain in the ass -_- |
|
what? |
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)If the PR contains API changes (otherwise, you can delete this passage)
New classes:
self._id_attrsand corresponding documentation__init__accepts**_kwargsAdded 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 variablesREADME.rstandREADME_RAW.rst(including the badge), as well astelegram.constants.BOT_API_VERSIONtg.ext.Botfor new methods that either accept areply_markupin some form or have a return type that is/containstelegram.Message