Thanks to visit codestin.com
Credit goes to github.com

Skip to content

API 6.3 #3346

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 34 commits into from
Nov 22, 2022
Merged

API 6.3 #3346

merged 34 commits into from
Nov 22, 2022

Conversation

harshil21
Copy link
Member

@harshil21 harshil21 commented Nov 6, 2022

Gathering all commits/fixes/PRs for the new and big 6.3 update.

  • Update tests for new forum methods - see here
  • revert changes to the test config

Checklist for PRs

  • Added .. versionadded:: version, .. versionchanged:: version or .. deprecated:: version to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)
  • Created new or adapted existing unit tests
  • Documented code changes according to the CSI standard
  • Added myself alphabetically to AUTHORS.rst (optional)
  • Added new classes & modules to the docs and all suitable __all__ s

If the PR contains API changes (otherwise, you can delete this passage)

  • New classes:

    • Added self._id_attrs and corresponding documentation
    • __init__ accepts **_kwargs
  • Added new shortcuts:

    • In Chat & User for all methods that accept chat/user_id
    • In Message for all methods that accept chat_id and message_id
    • For new Message shortcuts: Added quote argument if methods accepts reply_to_message_id
    • In CallbackQuery for all methods that accept either chat_id and message_id or inline_message_id
  • If relevant:

    • Added new constants at telegram.constants and shortcuts to them as class variables
    • Link new and existing constants in docstrings instead of hard coded number and strings
    • Add new message types to Message.effective_attachment
    • Added new handlers for new update types
      • Add the handlers to the warning loop in the ConversationHandler
    • Added new filters for new message (sub)types
    • Added or updated documentation for the changed class(es) and/or method(s)
    • Added or updated bot_methods.rst
    • Updated the Bot API version number in all places: README.rst and README_RAW.rst (including the badge), as well as telegram.constants.BOT_API_VERSION
    • Added logic for arbitrary callback data in tg.ext.Bot for new methods that either accept a reply_markup in some form or have a return type that is/contains telegram.Message

@harshil21 harshil21 added the ⚙️ bot-api affected functionality: bot-api label Nov 6, 2022
@harshil21 harshil21 added this to the v20.0a5 milestone Nov 6, 2022
@harshil21 harshil21 linked an issue Nov 6, 2022 that may be closed by this pull request
13 tasks
@Bibo-Joshi
Copy link
Member

Requesting reviews from everyone 🕺 Will try to review sometime this weekend
Smaller stuff can be pushed directly into this branch by everyone IMO. For things that you feel like they need discussion, leave a comment :)

Copy link

@github-actions github-actions bot left a 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 :)

the TODO was asking about whether we should test
a `str` identifier of a chat (right now only `int`
is tested)

It was agreed that additional tests were not needed
and we will trust Telegram's behaviour
colors are automatically converted to `int`.
User should be able to see that we mean HEX colors
listed in Telegram API
Copy link
Member

@lemontree210 lemontree210 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Obviously, given my lack of in-depth knowledge, this is not mostly nitpicking: this is only nitpicking 😄

Copy link
Member

@lemontree210 lemontree210 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes suggested based on my work on #3351 . I can implement the changes myself, should there be no objections

Copy link
Member

@Bibo-Joshi Bibo-Joshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Went through the code (but skipped the tests). Only have two comments :)

Copy link
Member

@Poolitzer Poolitzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didnt see an issue here, gj us claps on the back

Copy link
Member

@clot27 clot27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Bibo-Joshi Bibo-Joshi merged commit caacafa into master Nov 22, 2022
@Bibo-Joshi Bibo-Joshi deleted the api_6.3_update branch November 22, 2022 09:43
@Poolitzer Poolitzer mentioned this pull request Nov 25, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Nov 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
⚙️ bot-api affected functionality: bot-api
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature] Bot API 6.3 update
5 participants