diff --git a/src/Funogram.Generator/out/types.json b/src/Funogram.Generator/out/types.json index 7a49c31..3b76334 100644 --- a/src/Funogram.Generator/out/types.json +++ b/src/Funogram.Generator/out/types.json @@ -9,7 +9,7 @@ { "OriginalName": "update_id", "ConvertedName": "UpdateId", - "Description": "The update\u0027s unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you\u0027re using webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.", + "Description": "The update\u0027s unique identifier. Update identifiers start from a certain positive number and increase sequentially. This identifier becomes especially handy if you\u0027re using webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.", "OriginalFieldType": "Integer", "ConvertedFieldType": "int64", "Optional": false @@ -25,7 +25,7 @@ { "OriginalName": "edited_message", "ConvertedName": "EditedMessage", - "Description": "New version of a message that is known to the bot and was edited", + "Description": "New version of a message that is known to the bot and was edited. This update may at times be triggered by changes to message fields that are either unavailable or not actively used by your bot.", "OriginalFieldType": "Message", "ConvertedFieldType": "Message", "Optional": true @@ -41,7 +41,7 @@ { "OriginalName": "edited_channel_post", "ConvertedName": "EditedChannelPost", - "Description": "New version of a channel post that is known to the bot and was edited", + "Description": "New version of a channel post that is known to the bot and was edited. This update may at times be triggered by changes to message fields that are either unavailable or not actively used by your bot.", "OriginalFieldType": "Message", "ConvertedFieldType": "Message", "Optional": true @@ -57,7 +57,7 @@ { "OriginalName": "message_reaction_count", "ConvertedName": "MessageReactionCount", - "Description": "Reactions to a message with anonymous reactions were changed. The bot must be an administrator in the chat and must explicitly specify \u0022message_reaction_count\u0022 in the list of allowed_updates to receive these updates.", + "Description": "Reactions to a message with anonymous reactions were changed. The bot must be an administrator in the chat and must explicitly specify \u0022message_reaction_count\u0022 in the list of allowed_updates to receive these updates. The updates are grouped and can be sent with delay up to a few minutes.", "OriginalFieldType": "MessageReactionCountUpdated", "ConvertedFieldType": "MessageReactionCountUpdated", "Optional": true @@ -105,7 +105,7 @@ { "OriginalName": "poll", "ConvertedName": "Poll", - "Description": "New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot", + "Description": "New poll state. Bots receive only updates about manually stopped polls and polls, which are sent by the bot", "OriginalFieldType": "Poll", "ConvertedFieldType": "Poll", "Optional": true @@ -3469,7 +3469,7 @@ { "OriginalName": "selective", "ConvertedName": "Selective", - "Description": "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 object; 2) if the bot\u0027s message is a reply (has reply_to_message_id), sender of the original message.\n\nExample: A user requests to change the bot\u0027s language, bot replies to the request with a keyboard to select the new language. Other users in the group don\u0027t see the keyboard.", + "Description": "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 object; 2) if the bot\u0027s message is a reply to a message in the same chat and forum topic, sender of the original message.\n\nExample: A user requests to change the bot\u0027s language, bot replies to the request with a keyboard to select the new language. Other users in the group don\u0027t see the keyboard.", "OriginalFieldType": "Boolean", "ConvertedFieldType": "bool", "Optional": true @@ -3480,7 +3480,7 @@ }, { "Name": "KeyboardButton", - "Description": "This object represents one button of the reply keyboard. For simple text buttons, String can be used instead of this object to specify the button text. The optional fields web_app, request_users, request_chat, request_contact, request_location, and request_poll are mutually exclusive.\nNote:request_contact and request_location options will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.\nNote:request_poll option will only work in Telegram versions released after 23 January, 2020. Older clients will display unsupported message.\nNote:web_app option will only work in Telegram versions released after 16 April, 2022. Older clients will display unsupported message.\nNote:request_users and request_chat options will only work in Telegram versions released after 3 February, 2023. Older clients will display unsupported message.", + "Description": "This object represents one button of the reply keyboard. For simple text buttons, String can be used instead of this object to specify the button text. The optional fields web_app, request_users, request_chat, request_contact, request_location, and request_poll are mutually exclusive.\nNote:request_users and request_chat options will only work in Telegram versions released after 3 February, 2023. Older clients will display unsupported message.", "Kind": { "Case": "Fields", "Fields": [ @@ -3700,7 +3700,7 @@ { "OriginalName": "selective", "ConvertedName": "Selective", - "Description": "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 object; 2) if the bot\u0027s message is a reply (has reply_to_message_id), sender of the original message.\n\nExample: 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\u0027t voted yet.", + "Description": "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 object; 2) if the bot\u0027s message is a reply to a message in the same chat and forum topic, sender of the original message.\n\nExample: 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\u0027t voted yet.", "OriginalFieldType": "Boolean", "ConvertedFieldType": "bool", "Optional": true @@ -3711,7 +3711,7 @@ }, { "Name": "InlineKeyboardMarkup", - "Description": "This object represents an inline keyboard that appears right next to the message it belongs to.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.", + "Description": "This object represents an inline keyboard that appears right next to the message it belongs to.", "Kind": { "Case": "Fields", "Fields": [ @@ -3746,7 +3746,7 @@ { "OriginalName": "url", "ConvertedName": "Url", - "Description": "HTTP or tg:// URL to be opened when the button is pressed. Links tg://user?id=\u003Cuser_id\u003E can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.", + "Description": "HTTP or tg:// URL to be opened when the button is pressed. Links tg://user?id=\u003Cuser_id\u003E can be used to mention a user by their identifier without using a username, if this is allowed by their privacy settings.", "OriginalFieldType": "String", "ConvertedFieldType": "string", "Optional": true @@ -4006,7 +4006,7 @@ { "OriginalName": "selective", "ConvertedName": "Selective", - "Description": "Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot\u0027s message is a reply (has reply_to_message_id), sender of the original message.", + "Description": "Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot\u0027s message is a reply to a message in the same chat and forum topic, sender of the original message.", "OriginalFieldType": "Boolean", "ConvertedFieldType": "bool", "Optional": true @@ -7464,7 +7464,7 @@ }, { "Name": "InlineQueryResultAudio", - "Description": "Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.", "Kind": { "Case": "Fields", "Fields": [ @@ -7563,7 +7563,7 @@ }, { "Name": "InlineQueryResultVoice", - "Description": "Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.", "Kind": { "Case": "Fields", "Fields": [ @@ -7654,7 +7654,7 @@ }, { "Name": "InlineQueryResultDocument", - "Description": "Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method.", "Kind": { "Case": "Fields", "Fields": [ @@ -7777,7 +7777,7 @@ }, { "Name": "InlineQueryResultLocation", - "Description": "Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.", "Kind": { "Case": "Fields", "Fields": [ @@ -7900,7 +7900,7 @@ }, { "Name": "InlineQueryResultVenue", - "Description": "Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue.", "Kind": { "Case": "Fields", "Fields": [ @@ -8031,7 +8031,7 @@ }, { "Name": "InlineQueryResultContact", - "Description": "Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.", "Kind": { "Case": "Fields", "Fields": [ @@ -8130,7 +8130,7 @@ }, { "Name": "InlineQueryResultGame", - "Description": "Represents a Game.\nNote: This will only work in Telegram versions released after October 1, 2016. Older clients will not display any inline results if a game result is among them.", + "Description": "Represents a Game.", "Kind": { "Case": "Fields", "Fields": [ @@ -8430,7 +8430,7 @@ }, { "Name": "InlineQueryResultCachedSticker", - "Description": "Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker.\nNote: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them.", + "Description": "Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker.", "Kind": { "Case": "Fields", "Fields": [ @@ -8481,7 +8481,7 @@ }, { "Name": "InlineQueryResultCachedDocument", - "Description": "Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file.", "Kind": { "Case": "Fields", "Fields": [ @@ -8663,7 +8663,7 @@ }, { "Name": "InlineQueryResultCachedVoice", - "Description": "Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.", "Kind": { "Case": "Fields", "Fields": [ @@ -8746,7 +8746,7 @@ }, { "Name": "InlineQueryResultCachedAudio", - "Description": "Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.", + "Description": "Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.", "Kind": { "Case": "Fields", "Fields": [ @@ -9294,7 +9294,7 @@ }, { "Name": "SentWebAppMessage", - "Description": "Describes an inline message sent by a Web App on behalf of a user.\nYour bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. Please note that users will need Telegram v.4.0 or higher to use payments (released on May 18, 2017).", + "Description": "Describes an inline message sent by a Web App on behalf of a user.\nYour bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot.", "Kind": { "Case": "Fields", "Fields": [ diff --git a/src/Funogram.Telegram/Directory.Build.props b/src/Funogram.Telegram/Directory.Build.props index 67083d4..a7ec561 100644 --- a/src/Funogram.Telegram/Directory.Build.props +++ b/src/Funogram.Telegram/Directory.Build.props @@ -1,6 +1,6 @@ - 6.9.0.1 + 7.0.0.0 Nikolay Matyushin Funogram.Telegram Funogram.Telegram diff --git a/src/Funogram.Telegram/Types.fs b/src/Funogram.Telegram/Types.fs index bc6ecc6..abbc7b1 100644 --- a/src/Funogram.Telegram/Types.fs +++ b/src/Funogram.Telegram/Types.fs @@ -74,25 +74,25 @@ and EditMessageResult = /// At most one of the optional parameters can be present in any given update. and [] Update = { - /// The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially. + /// The update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This identifier becomes especially handy if you're using webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially. [] UpdateId: int64 /// New incoming message of any kind - text, photo, sticker, etc. [] Message: Message option - /// New version of a message that is known to the bot and was edited + /// New version of a message that is known to the bot and was edited. This update may at times be triggered by changes to message fields that are either unavailable or not actively used by your bot. [] EditedMessage: Message option /// New incoming channel post of any kind - text, photo, sticker, etc. [] ChannelPost: Message option - /// New version of a channel post that is known to the bot and was edited + /// New version of a channel post that is known to the bot and was edited. This update may at times be triggered by changes to message fields that are either unavailable or not actively used by your bot. [] EditedChannelPost: Message option /// A reaction to a message was changed by a user. The bot must be an administrator in the chat and must explicitly specify "message_reaction" in the list of allowed_updates to receive these updates. The update isn't received for reactions set by bots. [] MessageReaction: MessageReactionUpdated option - /// Reactions to a message with anonymous reactions were changed. The bot must be an administrator in the chat and must explicitly specify "message_reaction_count" in the list of allowed_updates to receive these updates. + /// Reactions to a message with anonymous reactions were changed. The bot must be an administrator in the chat and must explicitly specify "message_reaction_count" in the list of allowed_updates to receive these updates. The updates are grouped and can be sent with delay up to a few minutes. [] MessageReactionCount: MessageReactionCountUpdated option /// New incoming inline query @@ -110,7 +110,7 @@ and [] Update = /// New incoming pre-checkout query. Contains full information about checkout [] PreCheckoutQuery: PreCheckoutQuery option - /// New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot + /// New poll state. Bots receive only updates about manually stopped polls and polls, which are sent by the bot [] Poll: Poll option /// A user changed their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself. @@ -1911,7 +1911,7 @@ and [] ReplyKeyboardMarkup = /// The placeholder to be shown in the input field when the keyboard is active; 1-64 characters [] InputFieldPlaceholder: string option - /// 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 object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message. + /// 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 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. /// /// 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. [] @@ -1928,9 +1928,6 @@ and [] ReplyKeyboardMarkup = } /// This object represents one button of the reply keyboard. For simple text buttons, String can be used instead of this object to specify the button text. The optional fields web_app, request_users, request_chat, request_contact, request_location, and request_poll are mutually exclusive. -/// Note:request_contact and request_location options will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message. -/// Note:request_poll option will only work in Telegram versions released after 23 January, 2020. Older clients will display unsupported message. -/// Note:web_app option will only work in Telegram versions released after 16 April, 2022. Older clients will display unsupported message. /// Note:request_users and request_chat options will only work in Telegram versions released after 3 February, 2023. Older clients will display unsupported message. and [] KeyboardButton = { @@ -2049,7 +2046,7 @@ and [] ReplyKeyboardRemove = /// Requests clients to remove the custom keyboard (user will not be able to summon this keyboard; if you want to hide the keyboard from sight but keep it accessible, use one_time_keyboard in ReplyKeyboardMarkup) [] RemoveKeyboard: bool - /// 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 object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message. + /// 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 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. /// /// 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. [] @@ -2062,7 +2059,6 @@ and [] ReplyKeyboardRemove = } /// This object represents an inline keyboard that appears right next to the message it belongs to. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message. and [] InlineKeyboardMarkup = { /// Array of button rows, each represented by an Array of InlineKeyboardButton objects @@ -2080,7 +2076,7 @@ and [] InlineKeyboardButton = /// Label text on the button [] Text: string - /// HTTP or tg:// URL to be opened when the button is pressed. Links tg://user?id= can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings. + /// HTTP or tg:// URL to be opened when the button is pressed. Links tg://user?id= can be used to mention a user by their identifier without using a username, if this is allowed by their privacy settings. [] Url: string option /// Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes @@ -2228,7 +2224,7 @@ and [] ForceReply = /// The placeholder to be shown in the input field when the reply is active; 1-64 characters [] InputFieldPlaceholder: string option - /// Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message. + /// Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the 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. [] Selective: bool option } @@ -4043,7 +4039,6 @@ and [] InlineQueryResultVideo = } /// Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultAudio = { /// Type of the result, must be audio @@ -4096,7 +4091,6 @@ and [] InlineQueryResultAudio = } /// Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultVoice = { /// Type of the result, must be voice @@ -4145,7 +4139,6 @@ and [] InlineQueryResultVoice = } /// Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultDocument = { /// Type of the result, must be document @@ -4210,7 +4203,6 @@ and [] InlineQueryResultDocument = } /// Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultLocation = { /// Type of the result, must be location @@ -4275,7 +4267,6 @@ and [] InlineQueryResultLocation = } /// Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultVenue = { /// Type of the result, must be venue @@ -4344,7 +4335,6 @@ and [] InlineQueryResultVenue = } /// Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultContact = { /// Type of the result, must be contact @@ -4397,7 +4387,6 @@ and [] InlineQueryResultContact = } /// Represents a Game. -/// Note: This will only work in Telegram versions released after October 1, 2016. Older clients will not display any inline results if a game result is among them. and [] InlineQueryResultGame = { /// Type of the result, must be game @@ -4558,7 +4547,6 @@ and [] InlineQueryResultCachedMpeg4Gif = } /// Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker. -/// Note: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them. and [] InlineQueryResultCachedSticker = { /// Type of the result, must be sticker @@ -4587,7 +4575,6 @@ and [] InlineQueryResultCachedSticker = } /// Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultCachedDocument = { /// Type of the result, must be document @@ -4684,7 +4671,6 @@ and [] InlineQueryResultCachedVideo = } /// Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultCachedVoice = { /// Type of the result, must be voice @@ -4729,7 +4715,6 @@ and [] InlineQueryResultCachedVoice = } /// Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio. -/// Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them. and [] InlineQueryResultCachedAudio = { /// Type of the result, must be audio @@ -5015,7 +5000,7 @@ and [] ChosenInlineResult = } /// Describes an inline message sent by a Web App on behalf of a user. -/// Your bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. Please note that users will need Telegram v.4.0 or higher to use payments (released on May 18, 2017). +/// Your bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. and [] SentWebAppMessage = { /// Identifier of the sent inline message. Available only if there is an inline keyboard attached to the message.