@telegram.ts/types 1.24.0 → 1.25.1

package/src/messageTypes.d.ts

@@ -29,7 +29,7 @@ export declare namespace Message {
   interface ServiceMessage {
     /** Unique message identifier inside this chat. In specific instances (e.g., message containing a video sent to a big chat), the server might automatically schedule a message instead of sending it immediately. In such cases, this field will be 0 and the relevant message will be unusable until it is actually sent */
     message_id: number;
-    /** Unique identifier of a message thread or a forum topic to which the message belongs; for supergroups only */
+    /** Unique identifier of a message thread or forum topic to which the message belongs; for supergroups and private chats only */
     message_thread_id?: number;
     /** Sender of the message; may be empty for messages sent to channels. For backward compatibility, if the message was sent on behalf of a chat, the field contains a fake sender user in non-channel chats. */
     from?: User;
@@ -41,7 +41,7 @@ export declare namespace Message {
     business_connection_id?: string;
     /** Chat the message belongs to */
     chat: Chat;
-    /** True, if the message is sent to a forum topic */
+    /** True, if the message is sent to a topic in a forum supergroup or a private chat with the bot */
     is_topic_message?: boolean;
     /** Information about the direct messages chat topic that contains the message */
     direct_messages_topic?: DirectMessagesTopic;
@@ -101,7 +101,9 @@ export declare namespace Message {
     has_media_spoiler?: true;
   }
 
-  export type TextMessage = CommonMessage & MsgWith<"text">;
+  export type TextMessage = CommonMessage &
+    MsgWith<"text"> &
+    Partial<MsgWith<"entities">>;
   export type AudioMessage = CaptionableMessage & MsgWith<"audio">;
   export type DocumentMessage = CaptionableMessage & MsgWith<"document">;
   export type AnimationMessage = DocumentMessage & MsgWith<"animation">;
@@ -196,6 +198,8 @@ export declare namespace Message {
     MsgWith<"giveaway_completed">;
   export type GiftMessage = ServiceMessage & MsgWith<"gift">;
   export type UniqueGiftMessage = ServiceMessage & MsgWith<"unique_gift">;
+  export type GiftUpgradeSentMessage = ServiceMessage &
+    MsgWith<"gift_upgrade_sent">;
   export type PaidMessagePriceChangedMessage = ServiceMessage &
     MsgWith<"paid_message_price_changed">;
   export type VideoChatScheduledMessage = ServiceMessage &
@@ -334,6 +338,8 @@ export interface Message extends Message.MediaMessage {
   giveaway_completed?: GiveawayCompleted;
   /** Service message: a regular gift was sent or received */
   gift?: GiftInfo;
+  /** Service message: upgrade of a gift was purchased after the gift was sent */
+  gift_upgrade_sent?: GiftInfo;
   /** Service message: a unique gift was sent or received */
   unique_gift?: UniqueGiftInfo;
   /** Service message: the price for paid messages has changed in the chat */
@@ -442,7 +448,7 @@ Please note:
 - Inside `pre` and `code` entities, all '`' and '\' characters must be escaped with a preceding '\' character.
 - Inside the `(...)` part of the inline link and custom emoji definition, all ')' and '\' must be escaped with a preceding '\' character.
 - In all other places characters '_', '*', '[', ']', '(', ')', '~', '`', '>', '#', '+', '-', '=', '|', '{', '}', '.', '!' must be escaped with the preceding character '\'.
-- In case of ambiguity between `italic` and `underline` entities `__` is always greadily treated from left to right as beginning or end of an `underline` entity, so instead of `___italic underline___` use `___italic underline_**__`, adding an empty bold entity as a separator.
+- In case of ambiguity between `italic` and `underline` entities `__` is always greedily treated from left to right as beginning or end of an `underline` entity, so instead of `___italic underline___` use `___italic underline_**__`, adding an empty bold entity as a separator.
 - A valid emoji must be provided as an alternative value for the custom emoji. The emoji will be shown instead of the custom emoji in places where a custom emoji cannot be displayed (e.g., system notifications) or if the message is forwarded by a non-premium user. It is recommended to use the emoji from the emoji field of the custom emoji sticker.
 - Custom emoji entities can only be used by bots that purchased additional usernames on Fragment.
 
@@ -496,7 +502,7 @@ Please note:
 
 - Entities must not be nested, use parse mode MarkdownV2 instead.
 - There is no way to specify “underline”, “strikethrough”, “spoiler”, “blockquote”, “expandable_blockquote” and “custom_emoji” entities, use parse mode MarkdownV2 instead.
-- To escape characters '_', '*', '`', '[' outside of an entity, prepend the characters '\' before them.
+- To escape character '_', '*', '`', '[' outside of an entity, prepend the characters '\' before them.
 - Escaping inside entities is not allowed, so entity must be closed first and reopened again: use `_snake_\__case_` for italic `snake_case` and `*2*\**2=4*` for bold `2*2=4`. */
 export type ParseMode = "Markdown" | "MarkdownV2" | "HTML";
 
@@ -1028,6 +1034,8 @@ export interface MessageAutoDeleteTimerChanged {
 export interface ForumTopicCreated {
   /** Name of the topic */
   name: string;
+  /** True, if the name of the topic wasn't specified explicitly by its creator and likely needs to be changed by the bot */
+  is_name_implicit?: true;
   /** Color of the topic icon in RGB format */
   icon_color: number;
   /** Unique identifier of the custom emoji shown as the topic icon */