Fixing tests and content types for Telegram Bot API 7.2 update #1453
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
✔️ Changelog found.Thank you for adding a description of the changes |
|
JrooTJunior
reviewed
Apr 7, 2024
| @@ -238,6 +239,8 @@ class Message(MaybeInaccessibleMessage): | |||
| """*Optional*. Message is an invoice for a `payment <https://core.telegram.org/bots/api#payments>`_, information about the invoice. `More about payments » <https://core.telegram.org/bots/api#payments>`_""" | |||
| successful_payment: Optional[SuccessfulPayment] = None | |||
| """*Optional*. Message is a service message about a successful payment, information about the payment. `More about payments » <https://core.telegram.org/bots/api#payments>`_""" | |||
| shared_user: Optional[SharedUser] = None | |||
| @@ -628,6 +633,12 @@ def content_type(self) -> str: | |||
| return ContentType.WRITE_ACCESS_ALLOWED | |||
| if self.boost_added: | |||
| return ContentType.BOOST_ADDED | |||
| if self.business_connection_id: | |||
| @@ -628,6 +633,12 @@ def content_type(self) -> str: | |||
| return ContentType.WRITE_ACCESS_ALLOWED | |||
| if self.boost_added: | |||
| return ContentType.BOOST_ADDED | |||
| if self.business_connection_id: | |||
| return ContentType.BUSINESS_CONNECTION_ID | |||
| if self.is_from_offline: | |||
| return ContentType.BUSINESS_CONNECTION_ID | ||
| if self.is_from_offline: | ||
| return ContentType.IS_FROM_OFFLINE | ||
| if self.sender_business_bot: |
JrooTJunior
added a commit
that referenced
this pull request
Apr 22, 2024
* Added base support of Bot API 7.2 * Added base support of Bot API 7.2 * Fixing tests and content types for Telegram Bot API 7.2 update (#1453) * Fixing tests and content types for Telegram Bot API 7.2 * Adding changelog for 1453 PR * Fixes + coverage * Replace `BusinessConnection.date` type * Reformat code * Refactor UserContextMiddleware to use EventContext class This update significantly refactors UserContextMiddleware to leverage a new class, EventContext. Instead of resolving event context as a tuple, it now produces an instance of EventContext. Additional adjustments include supporting a business connection ID for event context identification and facilitating backwards compatibility. Tests and other files were also updated accordingly for these changes. * Cover FSM key builder (business_connection_id * Added changelog --------- Co-authored-by: RoLOQ <roman.fedunn@gmail.com>
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.
Description
SHARED_USERinContentTypeenumFixes # (issue)
#1446
Type of change
* InputSticker now requires format as in Telegram Bot API
How Has This Been Tested?
Test Configuration:
Checklist: