npm - @grom.js/bot-api-spec - Versions diffs - 0.3.1 → 0.4.0 - Mend

@grom.js/bot-api-spec 0.3.1 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (4) hide show

package/README.md CHANGED Viewed

@@ -25,7 +25,7 @@ Below are the rules how we map type of a field/parameter to the `ValueType`:
 - _Type_ is _String_ — `{ type: 'str' }`
 - _Type_ is _Integer_ — `{ type: 'int32' }`
-- _Type_ is _Integer_ and _Description_ says "...may have more than 32 significant bits...but it has at most 52 significant bits..." — `{ type: 'int52' }`
+- _Type_ is _Integer_ and _Description_ says "...may have more than 32 significant bits...but it has at most 52 significant bits..." — `{ type: 'int53' }`
 - _Type_ is _Boolean_ — `{ type: 'bool' }`
 - _Type_ is _True_ — `{ type: 'bool', literal: true }`
 - _Type_ is _Float_ — `{ type: 'float' }`
@@ -41,4 +41,4 @@ Objects also include descriptions of the API types, methods, fields, and paramet
 - Description is an object with a single `markdown` property, a string containing the description in Markdown format with formatting (**bold**, _italic_, etc.) and links preserved.
 - "_Optional._" prefix in field descriptions is omitted; instead, the `required` property is set to `false` for such fields.
 - "JSON-serialized..." in field/parameter descriptions is omitted; instead, the `jsonSerialized` property is set to `true` for such fields/parameters.
-- "...may have more than 32 significant bits...but it has at most 52 significant bits..." in _Integer_ field/parameter descriptions is omitted; instead, `type` is set to `int52` for such fields/parameters.
+- "...may have more than 32 significant bits...but it has at most 52 significant bits..." in _Integer_ field/parameter descriptions is omitted; instead, `type` is set to `int53` for such fields/parameters (as per [TDLib](https://core.telegram.org/tdlib/docs/td__api_8h.html#a6f57ab89c6371535f0fb7fec2d770126)).

package/dist/index.d.ts CHANGED Viewed

@@ -83,7 +83,7 @@ interface Description {
 /**
  * Type of a value.
  */
-type ValueType = ValueTypeString | ValueTypeBoolean | ValueTypeInteger32 | ValueTypeInteger52 | ValueTypeFloat | ValueTypeInputFile | ValueTypeApiType | ValueTypeArray | ValueTypeUnion;
+type ValueType = ValueTypeString | ValueTypeBoolean | ValueTypeInteger32 | ValueTypeInteger53 | ValueTypeFloat | ValueTypeInputFile | ValueTypeApiType | ValueTypeArray | ValueTypeUnion;
 /**
  * `String` value type.
  */
@@ -110,8 +110,8 @@ interface ValueTypeInteger32 {
  * at most 52 significant bits, so a 64-bit integer or double-precision float
  * type are safe for storing values of this type.
  */
-interface ValueTypeInteger52 {
-  type: 'int52';
+interface ValueTypeInteger53 {
+  type: 'int53';
 }
 /**
  * `Float` value type.
@@ -598,4 +598,4 @@ declare const types: {
   GameHighScore: ApiType;
 };
 //#endregion
-export { ApiMethod, ApiType, ApiTypeObject, ApiTypeOneOf, Description, FieldOrParam, ValueType, ValueTypeApiType, ValueTypeArray, ValueTypeBoolean, ValueTypeFloat, ValueTypeInputFile, ValueTypeInteger32, ValueTypeInteger52, ValueTypeString, ValueTypeUnion, methods, types };
+export { ApiMethod, ApiType, ApiTypeObject, ApiTypeOneOf, Description, FieldOrParam, ValueType, ValueTypeApiType, ValueTypeArray, ValueTypeBoolean, ValueTypeFloat, ValueTypeInputFile, ValueTypeInteger32, ValueTypeInteger53, ValueTypeString, ValueTypeUnion, methods, types };

package/dist/index.js CHANGED Viewed

@@ -1,7 +1,7 @@
 //#region src/bot-api/methods.gen.ts
 const getUpdates = {
 	name: "getUpdates",
-	description: { markdown: "Use this method to receive incoming updates using long polling ([wiki](https://en.wikipedia.org/wiki/Push_technology#Long_polling)). Returns an Array of [Update](https://core.telegram.org/bots/api#update) objects.\n\n> **Notes**  \n> **1.** This method will not work if an outgoing webhook is set up.  \n> **2.** In order to avoid getting duplicate updates, recalculate _offset_ after each server response." },
+	description: { markdown: "Use this method to receive incoming updates using long polling ([wiki](https://en.wikipedia.org/wiki/Push_technology#Long_polling)). Returns an Array of [Update](https://core.telegram.org/bots/api#update) objects.\n\n> **Notes**\n> \n> **1.** This method will not work if an outgoing webhook is set up.\n> \n> **2.** In order to avoid getting duplicate updates, recalculate _offset_ after each server response." },
 	parameters: [
 		{
 			name: "offset",
@@ -30,7 +30,7 @@ const getUpdates = {
 				type: "array",
 				of: { type: "str" }
 			},
-			description: { markdown: "An array of the update types you want your bot to receive. For example, specify `[\"message\", \"edited_channel_post\", \"callback_query\"]` to only receive updates of these types. See [Update](https://core.telegram.org/bots/api#update) for a complete list of available update types. Specify an empty list to receive all update types except _chat\\_member_, _message\\_reaction_, and _message\\_reaction\\_count_ (default). If not specified, the previous setting will be used.  \n  \nPlease note that this parameter doesn't affect updates created before the call to getUpdates, so unwanted updates may be received for a short period of time." },
+			description: { markdown: "An array of the update types you want your bot to receive. For example, specify `[\"message\", \"edited_channel_post\", \"callback_query\"]` to only receive updates of these types. See [Update](https://core.telegram.org/bots/api#update) for a complete list of available update types. Specify an empty list to receive all update types except _chat\\_member_, _message\\_reaction_, and _message\\_reaction\\_count_ (default). If not specified, the previous setting will be used.\n\nPlease note that this parameter doesn't affect updates created before the call to getUpdates, so unwanted updates may be received for a short period of time." },
 			required: false,
 			jsonSerialized: true
 		}
@@ -45,7 +45,7 @@ const getUpdates = {
 };
 const setWebhook = {
 	name: "setWebhook",
-	description: { markdown: "Use this method to specify a URL and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified URL, containing a JSON-serialized [Update](https://core.telegram.org/bots/api#update). In case of an unsuccessful request (a request with response [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) different from `2XY`), we will repeat the request and give up after a reasonable amount of attempts. Returns _True_ on success.\n\nIf you'd like to make sure that the webhook was set by you, you can specify secret data in the parameter _secret\\_token_. If specified, the request will contain a header “X-Telegram-Bot-Api-Secret-Token” with the secret token as content.\n\n> **Notes**  \n> **1.** You will not be able to receive updates using [getUpdates](https://core.telegram.org/bots/api#getupdates) for as long as an outgoing webhook is set up.  \n> **2.** To use a self-signed certificate, you need to upload your [public key certificate](https://core.telegram.org/bots/self-signed) using _certificate_ parameter. Please upload as InputFile, sending a String will not work.  \n> **3.** Ports currently supported _for webhooks_: **443, 80, 88, 8443**.\n> \n> If you're having any trouble setting up webhooks, please check out this [amazing guide to webhooks](https://core.telegram.org/bots/webhooks)." },
+	description: { markdown: "Use this method to specify a URL and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified URL, containing a JSON-serialized [Update](https://core.telegram.org/bots/api#update). In case of an unsuccessful request (a request with response [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) different from `2XY`), we will repeat the request and give up after a reasonable amount of attempts. Returns _True_ on success.\n\nIf you'd like to make sure that the webhook was set by you, you can specify secret data in the parameter _secret\\_token_. If specified, the request will contain a header “X-Telegram-Bot-Api-Secret-Token” with the secret token as content.\n\n> **Notes**\n> \n> **1.** You will not be able to receive updates using [getUpdates](https://core.telegram.org/bots/api#getupdates) for as long as an outgoing webhook is set up.\n> \n> **2.** To use a self-signed certificate, you need to upload your [public key certificate](https://core.telegram.org/bots/self-signed) using _certificate_ parameter. Please upload as InputFile, sending a String will not work.\n> \n> **3.** Ports currently supported _for webhooks_: **443, 80, 88, 8443**.\n> \n> If you're having any trouble setting up webhooks, please check out this [amazing guide to webhooks](https://core.telegram.org/bots/webhooks)." },
 	parameters: [
 		{
 			name: "url",
@@ -81,7 +81,7 @@ const setWebhook = {
 				type: "array",
 				of: { type: "str" }
 			},
-			description: { markdown: "An array of the update types you want your bot to receive. For example, specify `[\"message\", \"edited_channel_post\", \"callback_query\"]` to only receive updates of these types. See [Update](https://core.telegram.org/bots/api#update) for a complete list of available update types. Specify an empty list to receive all update types except _chat\\_member_, _message\\_reaction_, and _message\\_reaction\\_count_ (default). If not specified, the previous setting will be used.  \nPlease note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time." },
+			description: { markdown: "An array of the update types you want your bot to receive. For example, specify `[\"message\", \"edited_channel_post\", \"callback_query\"]` to only receive updates of these types. See [Update](https://core.telegram.org/bots/api#update) for a complete list of available update types. Specify an empty list to receive all update types except _chat\\_member_, _message\\_reaction_, and _message\\_reaction\\_count_ (default). If not specified, the previous setting will be used.\n\nPlease note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time." },
 			required: false,
 			jsonSerialized: true
 		},
@@ -4587,7 +4587,7 @@ const answerCallbackQuery = {
 		{
 			name: "url",
 			type: { type: "str" },
-			description: { markdown: "URL that will be opened by the user's client. If you have created a [Game](https://core.telegram.org/bots/api#game) and accepted the conditions via [@BotFather](https://t.me/botfather), specify the URL that opens your game - note that this will only work if the query comes from a [_callback\\_game_](https://core.telegram.org/bots/api#inlinekeyboardbutton) button.  \n  \nOtherwise, you may use links like `t.me/your_bot?start=XXXX` that open your bot with a parameter." },
+			description: { markdown: "URL that will be opened by the user's client. If you have created a [Game](https://core.telegram.org/bots/api#game) and accepted the conditions via [@BotFather](https://t.me/botfather), specify the URL that opens your game - note that this will only work if the query comes from a [_callback\\_game_](https://core.telegram.org/bots/api#inlinekeyboardbutton) button.\n\nOtherwise, you may use links like `t.me/your_bot?start=XXXX` that open your bot with a parameter." },
 			required: false,
 			jsonSerialized: false
 		},
@@ -6351,7 +6351,7 @@ const declineSuggestedPost = {
 };
 const deleteMessage = {
 	name: "deleteMessage",
-	description: { markdown: "Use this method to delete a message, including service messages, with the following limitations:  \n\\- A message can only be deleted if it was sent less than 48 hours ago.  \n\\- Service messages about a supergroup, channel, or forum topic creation can't be deleted.  \n\\- A dice message in a private chat can only be deleted if it was sent more than 24 hours ago.  \n\\- Bots can delete outgoing messages in private chats, groups, and supergroups.  \n\\- Bots can delete incoming messages in private chats.  \n\\- Bots granted _can\\_post\\_messages_ permissions can delete outgoing messages in channels.  \n\\- If the bot is an administrator of a group, it can delete any message there.  \n\\- If the bot has _can\\_delete\\_messages_ administrator right in a supergroup or a channel, it can delete any message there.  \n\\- If the bot has _can\\_manage\\_direct\\_messages_ administrator right in a channel, it can delete any message in the corresponding direct messages chat.  \nReturns _True_ on success." },
+	description: { markdown: "Use this method to delete a message, including service messages, with the following limitations:\n\n\\- A message can only be deleted if it was sent less than 48 hours ago.\n\n\\- Service messages about a supergroup, channel, or forum topic creation can't be deleted.\n\n\\- A dice message in a private chat can only be deleted if it was sent more than 24 hours ago.\n\n\\- Bots can delete outgoing messages in private chats, groups, and supergroups.\n\n\\- Bots can delete incoming messages in private chats.\n\n\\- Bots granted _can\\_post\\_messages_ permissions can delete outgoing messages in channels.\n\n\\- If the bot is an administrator of a group, it can delete any message there.\n\n\\- If the bot has _can\\_delete\\_messages_ administrator right in a supergroup or a channel, it can delete any message there.\n\n\\- If the bot has _can\\_manage\\_direct\\_messages_ administrator right in a channel, it can delete any message in the corresponding direct messages chat.\n\nReturns _True_ on success." },
 	parameters: [{
 		name: "chat_id",
 		type: {
@@ -6941,7 +6941,7 @@ const deleteStickerSet = {
 };
 const answerInlineQuery = {
 	name: "answerInlineQuery",
-	description: { markdown: "Use this method to send answers to an inline query. On success, _True_ is returned.  \nNo more than **50** results per query are allowed." },
+	description: { markdown: "Use this method to send answers to an inline query. On success, _True_ is returned.\n\nNo more than **50** results per query are allowed." },
 	parameters: [
 		{
 			name: "inline_query_id",
@@ -8043,7 +8043,7 @@ const methods = {
 const t = (apiType) => apiType;
 const Update = t({
 	name: "Update",
-	description: { markdown: "This [object](https://core.telegram.org/bots/api#available-types) represents an incoming update.  \nAt most **one** of the optional parameters can be present in any given update." },
+	description: { markdown: "This [object](https://core.telegram.org/bots/api#available-types) represents an incoming update.\n\nAt most **one** of the optional parameters can be present in any given update." },
 	fields: [
 		{
 			name: "update_id",
@@ -8362,7 +8362,7 @@ const User = t({
 	fields: [
 		{
 			name: "id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Unique identifier for this user or bot." },
 			required: true,
 			jsonSerialized: false
@@ -8465,7 +8465,7 @@ const Chat = t({
 	fields: [
 		{
 			name: "id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Unique identifier for this chat." },
 			required: true,
 			jsonSerialized: false
@@ -8533,7 +8533,7 @@ const ChatFullInfo = t({
 	fields: [
 		{
 			name: "id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Unique identifier for this chat." },
 			required: true,
 			jsonSerialized: false
@@ -8923,7 +8923,7 @@ const ChatFullInfo = t({
 		},
 		{
 			name: "linked_chat_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Unique identifier for the linked chat, i.e. the discussion group identifier for a channel and vice versa; for supergroups and channel chats." },
 			required: false,
 			jsonSerialized: false
@@ -9529,14 +9529,14 @@ const Message = t({
 		},
 		{
 			name: "migrate_to_chat_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "The group has been migrated to a supergroup with the specified identifier." },
 			required: false,
 			jsonSerialized: false
 		},
 		{
 			name: "migrate_from_chat_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "The supergroup has been migrated from a group with the specified identifier." },
 			required: false,
 			jsonSerialized: false
@@ -10676,7 +10676,7 @@ const Animation = t({
 		},
 		{
 			name: "file_size",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "File size in bytes." },
 			required: false,
 			jsonSerialized: false
@@ -10738,7 +10738,7 @@ const Audio = t({
 		},
 		{
 			name: "file_size",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "File size in bytes." },
 			required: false,
 			jsonSerialized: false
@@ -10799,7 +10799,7 @@ const Document = t({
 		},
 		{
 			name: "file_size",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "File size in bytes." },
 			required: false,
 			jsonSerialized: false
@@ -10911,7 +10911,7 @@ const Video = t({
 		},
 		{
 			name: "file_size",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "File size in bytes." },
 			required: false,
 			jsonSerialized: false
@@ -11003,7 +11003,7 @@ const Voice = t({
 		},
 		{
 			name: "file_size",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "File size in bytes." },
 			required: false,
 			jsonSerialized: false
@@ -11155,7 +11155,7 @@ const Contact = t({
 		},
 		{
 			name: "user_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Contact's user identifier in Telegram." },
 			required: false,
 			jsonSerialized: false
@@ -12218,7 +12218,7 @@ const SharedUser = t({
 	fields: [
 		{
 			name: "user_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Identifier of the shared user.  The bot may not have access to the user and could be unable to use this identifier, unless the user is already known to the bot by some other means." },
 			required: true,
 			jsonSerialized: false
@@ -12295,7 +12295,7 @@ const ChatShared = t({
 		},
 		{
 			name: "chat_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Identifier of the shared chat.  The bot may not have access to the chat and could be unable to use this identifier, unless the chat is already known to the bot by some other means." },
 			required: true,
 			jsonSerialized: false
@@ -12917,7 +12917,7 @@ const DirectMessagesTopic = t({
 	description: { markdown: "Describes a topic of a direct messages chat." },
 	fields: [{
 		name: "topic_id",
-		type: { type: "int52" },
+		type: { type: "int53" },
 		description: { markdown: "Unique identifier of the topic." },
 		required: true,
 		jsonSerialized: false
@@ -12978,7 +12978,7 @@ const File = t({
 		},
 		{
 			name: "file_size",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "File size in bytes." },
 			required: false,
 			jsonSerialized: false
@@ -13054,7 +13054,7 @@ const ReplyKeyboardMarkup = t({
 		{
 			name: "selective",
 			type: { type: "bool" },
-			description: { markdown: "Use this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the _text_ of the [Message](https://core.telegram.org/bots/api#message) object; 2) if the bot's message is a reply to a message in the same chat and forum topic, sender of the original message.  \n  \n_Example:_ A user requests to change the bot's language, bot replies to the request with a keyboard to select the new language. Other users in the group don't see the keyboard." },
+			description: { markdown: "Use this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the _text_ of the [Message](https://core.telegram.org/bots/api#message) object; 2) if the bot's message is a reply to a message in the same chat and forum topic, sender of the original message.\n\n_Example:_ A user requests to change the bot's language, bot replies to the request with a keyboard to select the new language. Other users in the group don't see the keyboard." },
 			required: false,
 			jsonSerialized: false
 		}
@@ -13297,7 +13297,7 @@ const ReplyKeyboardRemove = t({
 	}, {
 		name: "selective",
 		type: { type: "bool" },
-		description: { markdown: "Use this parameter if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the _text_ of the [Message](https://core.telegram.org/bots/api#message) object; 2) if the bot's message is a reply to a message in the same chat and forum topic, sender of the original message.  \n  \n_Example:_ A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet." },
+		description: { markdown: "Use this parameter if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the _text_ of the [Message](https://core.telegram.org/bots/api#message) object; 2) if the bot's message is a reply to a message in the same chat and forum topic, sender of the original message.\n\n_Example:_ A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet." },
 		required: false,
 		jsonSerialized: false
 	}]
@@ -13377,7 +13377,7 @@ const InlineKeyboardButton = t({
 		{
 			name: "switch_inline_query_current_chat",
 			type: { type: "str" },
-			description: { markdown: "If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. May be empty, in which case only the bot's username will be inserted.  \n  \nThis offers a quick way for the user to open your bot in inline mode in the same chat - good for selecting something from multiple options. Not supported in channels and for messages sent in channel direct messages chats and on behalf of a Telegram Business account." },
+			description: { markdown: "If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. May be empty, in which case only the bot's username will be inserted.\n\nThis offers a quick way for the user to open your bot in inline mode in the same chat - good for selecting something from multiple options. Not supported in channels and for messages sent in channel direct messages chats and on behalf of a Telegram Business account." },
 			required: false,
 			jsonSerialized: false
 		},
@@ -13407,14 +13407,14 @@ const InlineKeyboardButton = t({
 				type: "api-type",
 				name: "CallbackGame"
 			},
-			description: { markdown: "Description of the game that will be launched when the user presses the button.  \n  \n**NOTE:** This type of button **must** always be the first button in the first row." },
+			description: { markdown: "Description of the game that will be launched when the user presses the button.\n\n**NOTE:** This type of button **must** always be the first button in the first row." },
 			required: false,
 			jsonSerialized: false
 		},
 		{
 			name: "pay",
 			type: { type: "bool" },
-			description: { markdown: "Specify _True_, to send a [Pay button](https://core.telegram.org/bots/api#payments). Substrings “![⭐](//telegram.org/img/emoji/40/E2AD90.png)” and “XTR” in the buttons's text will be replaced with a Telegram Star icon.  \n  \n**NOTE:** This type of button **must** always be the first button in the first row and can only be used in invoice messages." },
+			description: { markdown: "Specify _True_, to send a [Pay button](https://core.telegram.org/bots/api#payments). Substrings “![⭐](//telegram.org/img/emoji/40/E2AD90.png)” and “XTR” in the buttons's text will be replaced with a Telegram Star icon.\n\n**NOTE:** This type of button **must** always be the first button in the first row and can only be used in invoice messages." },
 			required: false,
 			jsonSerialized: false
 		}
@@ -13427,7 +13427,7 @@ const LoginUrl = t({
 		{
 			name: "url",
 			type: { type: "str" },
-			description: { markdown: "An HTTPS URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in [Receiving authorization data](https://core.telegram.org/widgets/login#receiving-authorization-data).  \n  \n**NOTE:** You **must** always check the hash of the received data to verify the authentication and the integrity of the data as described in [Checking authorization](https://core.telegram.org/widgets/login#checking-authorization)." },
+			description: { markdown: "An HTTPS URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in [Receiving authorization data](https://core.telegram.org/widgets/login#receiving-authorization-data).\n\n**NOTE:** You **must** always check the hash of the received data to verify the authentication and the integrity of the data as described in [Checking authorization](https://core.telegram.org/widgets/login#checking-authorization)." },
 			required: true,
 			jsonSerialized: false
 		},
@@ -14369,7 +14369,7 @@ const ChatJoinRequest = t({
 		},
 		{
 			name: "user_chat_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Identifier of a private chat with the user who sent the join request.  The bot can use this identifier for 5 minutes to send messages until the join request is processed, assuming no other administrator contacted the user." },
 			required: true,
 			jsonSerialized: false
@@ -16503,7 +16503,7 @@ const BusinessConnection = t({
 		},
 		{
 			name: "user_chat_id",
-			type: { type: "int52" },
+			type: { type: "int53" },
 			description: { markdown: "Identifier of a private chat with the user who created the business connection." },
 			required: true,
 			jsonSerialized: false
@@ -16572,7 +16572,7 @@ const ResponseParameters = t({
 	description: { markdown: "Describes why a request was unsuccessful." },
 	fields: [{
 		name: "migrate_to_chat_id",
-		type: { type: "int52" },
+		type: { type: "int53" },
 		description: { markdown: "The group has been migrated to a supergroup with the specified identifier." },
 		required: false,
 		jsonSerialized: false
@@ -17562,7 +17562,7 @@ const InlineQueryResultsButton = t({
 		{
 			name: "start_parameter",
 			type: { type: "str" },
-			description: { markdown: "[Deep-linking](https://core.telegram.org/bots/features#deep-linking) parameter for the /start message sent to the bot when a user presses the button. 1-64 characters, only `A-Z`, `a-z`, `0-9`, `_` and `-` are allowed.  \n  \n_Example:_ An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer a [_switch\\_inline_](https://core.telegram.org/bots/api#inlinekeyboardmarkup) button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities." },
+			description: { markdown: "[Deep-linking](https://core.telegram.org/bots/features#deep-linking) parameter for the /start message sent to the bot when a user presses the button. 1-64 characters, only `A-Z`, `a-z`, `0-9`, `_` and `-` are allowed.\n\n_Example:_ An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer a [_switch\\_inline_](https://core.telegram.org/bots/api#inlinekeyboardmarkup) button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities." },
 			required: false,
 			jsonSerialized: false
 		}

package/package.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "name": "@grom.js/bot-api-spec",
   "type": "module",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "description": "Telegram Bot API specification as a collection of JavaScript objects in a custom format.",
   "license": "MIT",
   "repository": {